[vite:worker-import-meta-url] 'sep' is not exported by __vite-browser-external
See original GitHub issueI’m experiencing the error while doing vite build
for production:
It’s strange. Other imports from the path
module work.
Issue Analytics
- State:
- Created a year ago
- Comments:14 (10 by maintainers)
Top Results From Across the Web
Unable to build or serve application that imports @aws/sdk ...
Describe the bug I'm trying to migrate React application from CRA to Vite, but experience errors serving and building application.
Read more >Laravel Vite build error: 'resolve' is not exported by __vite ...
For this, when I run npm run build , I get the following error. > 'resolve' is not exported by __vite-browser-external, imported by...
Read more >Vite build failed on project with aws-sdk - DEV Community
Vite work greate on local development. But I got this error when build. 'request' is not exported by __vite-browser-external, ...
Read more >module has been externalized for browser compatibility
The requested module '/node_modules/googleapis/build/src/index.js?v=9d844668' does not provide an export named 'google'. I've seen in the browser/devtools ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Done. I’ve replicated the problem — https://github.com/astoilkov/electron-vite-worker-issue.
Run
yarn run build
and you will see this:This is causing an error when you run the app and click the “hello” text.
The issue is caused by:
graceful-fs
which is part of the array returned byrenderer.resolve()
functiongraceful-fs
should be used in the worker thread in order for the problem to appearAwesome! Thanks, @caoxiemeihao.