We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Vite
I have a content-script running on a https website, settings https flag on vite config is being ignored.
in vite.config.ts
server: { https: true, <-------------- port: 5173, hmr: { clientPort: 5173 }, proxy: { '/api': { target: 'http://localhost:3010', changeOrigin: true, rewrite: (path) => path.replace(/^\/api/, ''), }, }, }, })
and results in an error
Service worker registration failed. Status code: 3
"background": { "service_worker": "service-worker-loader.js", "type": "module" },
I believe this has to do with the encoded value in plugin-background.ts
if you can confirm this is the case i don't mind submitting a PR
No response
System: OS: Windows 11 CPU: (16) x64 Intel(R) Core(TM) i7-10870H CPU @ 2.20GHz Memory: 41 GB / 63 GB Binaries: Node: 20.7.0 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD pnpm: 8.12.0 - ~\AppData\Local\pnpm\pnpm.EXE Browsers: Edge: Chromium (120.0.2210.91)
blocking an upgrade
The text was updated successfully, but these errors were encountered:
@jacksteamdev if you'd like to guide me a bit here, I can take a shot at this issue
Sorry, something went wrong.
No branches or pull requests
Build tool
Vite
Where do you see the problem?
Describe the bug
I have a content-script running on a https website, settings https flag on vite config is being ignored.
Reproduction
in vite.config.ts
and results in an error
I believe this has to do with the encoded value in plugin-background.ts
if you can confirm this is the case i don't mind submitting a PR
Logs
No response
System Info
Severity
blocking an upgrade
The text was updated successfully, but these errors were encountered: