You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The build does output a worker in the specified output directory (defaulting to .next-worker).
This directory should contain everything that's required to run the worker (assets included).
But this is not so, as there are clear signs that files within .next-worker make use of files outside of the directory (making the dev/deployment of unbundled workers (--no-bundle) impossible).
I'm not sure how those files are not getting bundled by the esbuild build step 😕
We should make sure that they are actually bundled in, or if that's not possible, everything that the worker requires should just need to live in the output directory and no external file/dependency should be needed (in other words, I think that we need to make sure that wrangler dev --no-bundle works).
The text was updated successfully, but these errors were encountered:
dario-piotrowicz
changed the title
Bug 🐛 : everything that's needed should be in the output directory
🐛 Bug: everything that's needed should be in the output directory
Sep 20, 2024
The build does output a worker in the specified output directory (defaulting to
.next-worker
).This directory should contain everything that's required to run the worker (assets included).
But this is not so, as there are clear signs that files within
.next-worker
make use of files outside of the directory (making the dev/deployment of unbundled workers (--no-bundle
) impossible).For example:
pages.runtime.prod.js
fileI'm not sure how those files are not getting bundled by the esbuild build step 😕
We should make sure that they are actually bundled in, or if that's not possible, everything that the worker requires should just need to live in the output directory and no external file/dependency should be needed (in other words, I think that we need to make sure that
wrangler dev --no-bundle
works).The text was updated successfully, but these errors were encountered: