this repo has no description
10
fork

Configure Feed

Select the types of activity you want to include in your feed.

fix(indexer): run deno install in Dockerfile so node_modules exists at runtime

deno.json sets "nodeModulesDir": "manual", so Deno only resolves
npm: specifiers via a local ./node_modules. The previous Dockerfile
ran 'deno cache' alone, which populates the global module cache but
does not materialize node_modules — so at runtime the worker died
with ERR_MODULE_NOT_FOUND on @libsql/client/web in lib/db.ts.

Run 'deno install' first to lay down node_modules from the lockfile,
then cache the entrypoint as before.

Made-with: Cursor

+7 -3
+7 -3
worker.Dockerfile
··· 18 18 COPY lexicons ./lexicons 19 19 COPY utils.ts ./utils.ts 20 20 21 - # Resolve and cache all transitive imports at build time so the container 22 - # starts cold quickly and doesn't try to pull from JSR/NPM at runtime. 23 - RUN deno cache worker/indexer.ts 21 + # `deno.json` declares `"nodeModulesDir": "manual"`, so Deno expects an 22 + # actual ./node_modules to exist when resolving npm: specifiers (e.g. 23 + # @libsql/client/web). `deno install` materializes node_modules from the 24 + # lockfile without running lifecycle scripts. We then `deno cache` the 25 + # entrypoint so all JSR/HTTPS imports are pre-fetched into the global 26 + # cache and the container can start fully offline. 27 + RUN deno install && deno cache worker/indexer.ts 24 28 25 29 ENV DENO_ENV=production 26 30