-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Unable to write the service worker file" with vite-plugin-pwa #6302
Comments
I just ran into this as well, although I'm using the Astro version: @vite-pwa/astro. I get the following error:
|
Same problem here! |
Fix problems with vite Check oven-sh/bun#6302 Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
I downgraded from bun 1.0.4 to 1.0.3 for the time being. I see bun is currently at 1.0.6. I may try that and report back, in the off chance this was fixed. |
Fix problems with vite Check oven-sh/bun#6302 Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Doesn't work for me on Bun 1.0.7 |
Still not working on Bun version 1.0.9 |
Same on Bun version 1.0.11 |
I think it's this bug rollup/plugins#835 Workaround is to override the dependency in "overrides": {
"@rollup/plugin-node-resolve": "^15.2.3"
} |
Fixes a build error seen here: oven-sh/bun#6302
Does that go in our main package.json or in the vite-pwa? |
@Natetronn you can put it in your project's |
Same error on 1.0.11, although let me delete the lock and node_modules folder and install fresh an report back. Update: I deleted bun.lockb and node_modules folder and ran |
Fixed it for me thanks |
Fixes a build error seen here: oven-sh/bun#6302
What version of Bun is running?
1.0.4+745b6b94ee56cad24d475799690cc9a89957d15b
What platform is your computer?
Linux 5.15.90.1-microsoft-standard-WSL2 x86_64 x86_64
What steps can reproduce the bug?
bun run --bun vite build
with vite-plugin-pwa in vite.config.jsUnable to write the service worker file. ''
What is the expected behavior?
The build runs without errors
What do you see instead?
Additional information
Running the same command with version 1.0.3 works flawlessly.
The text was updated successfully, but these errors were encountered: