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
Everything was working fine until chrome released 130 and caused chaos with CSP. However I have upgraded the CRXJS package to "@crxjs/vite-plugin": "^2.0.0-beta.26" which have a fix for it. When I am starting the vite dev server, I am getting this error:
failed to load config from XX\vite.config.ts
Error when starting dev server:
TypeError: (0 , import_vite_plugin.crx) is not a functions
Any advise or workaround? I need to ship it ASAP as my extension is not working on production for many users.
Reproduction
Install ver 2.0.0-beta.26 and npm run dev.
Logs
No response
System Info
Windows 11, Chrome 130
Severity
blocking all usage of RPCE
The text was updated successfully, but these errors were encountered:
None of these solutions make a difference. crxjs seems unusable at this time.
The CJS build of Vite's Node API is deprecated. See https://vite.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.
failed to load config from redacted/packages/extension/vite.config.js
error when starting dev server:
TypeError: (0 , import_vite_plugin.crx) is not a function
Build tool
Rollup
Where do you see the problem?
Describe the bug
Everything was working fine until chrome released 130 and caused chaos with CSP. However I have upgraded the CRXJS package to
"@crxjs/vite-plugin": "^2.0.0-beta.26"
which have a fix for it. When I am starting the vite dev server, I am getting this error:failed to load config from XX\vite.config.ts
Error when starting dev server:
TypeError: (0 , import_vite_plugin.crx) is not a functions
Any advise or workaround? I need to ship it ASAP as my extension is not working on production for many users.
Reproduction
Install ver 2.0.0-beta.26 and npm run dev.
Logs
No response
System Info
Severity
blocking all usage of RPCE
The text was updated successfully, but these errors were encountered: