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 bundle is always written to a path where the outfile gets sliced. I think it makes sense to simply replace a leading slash, so we can have outFile: '_worker.js' instead of outFile: '/_worker.js'. Given that the entry point isn't allowed to have a leading slash, and need to be "neither absolute nor relative", it feels more natural to also not have a leading slash for the outFile.
The bundle is always written to a path where the
outfile
gets sliced. I think it makes sense to simply replace a leading slash, so we can haveoutFile: '_worker.js'
instead ofoutFile: '/_worker.js'
. Given that the entry point isn't allowed to have a leading slash, and need to be "neither absolute nor relative", it feels more natural to also not have a leading slash for the outFile.I think it's just the filename here:
vite-plugin-bundled-entry/src/index.ts
Lines 77 to 81 in 0673814
But I'm unsure about what this id slice does:
vite-plugin-bundled-entry/src/index.ts
Lines 126 to 129 in 0673814
Patching it in my node_modules to be
.replace(/^\//, "")
did the trick.The text was updated successfully, but these errors were encountered: