[vite] - No matching export for import pathToFileUrl
See original GitHub issueI’m using ViteJS as the build tool for a React application. When I try to run the vite dev server I get the error referenced in the title above. I’m not very well versed in the workings of awilix, but attempted to Google for that error. I was able to find a couple of things about loadModules and Windows tests, but didn’t seem to match this issue.
I setup a repo that isolates vite, awilix and jishida/react-awilix. I’m more than willing to do more investigating, but I’m kind of stuck with what to attempt next. Any help or advice would be greatly appreciated.
Error Message
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
No matching export in "browser-external:events" for import ...
yarn add events solved my issue. @web3-react/abstract-connector didn't add events as a dependency, and vite try to resolve dep from nodejs ...
Read more >__vite-browser-external | The AI Search Engine You Control
js error during build: Error: 'fileURLToPath' is not exported by __vite-browser-external, imported by node_modules/.pnpm/local-pkg@0.4.2/node_modules/local-pkg/ ...
Read more >Content Types - ESBuild
Imported variables are live bindings to variables in another file. They are not copies of those variables. So when esbuild bundles your code,...
Read more >JavaScript modules - MDN Web Docs
javascript.statements.export ... The map in imports is used as a fallback if there is no matching scope in the scoped map, or the...
Read more >Vue 3 + Vite 3 compatibility | Vue Forums - Syncfusion
✘ [ERROR] No matching export in "node_modules/.pnpm/vue@3.2.40/node_modules/vue/dist/vue.runtime.esm-bundler.js" for import "default" ...
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 Free
Top 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
I would think it’s something that should be fixed on Vite’s side? Webpack resolves the browser build by default just fine.
Ah, I think I got it. Found this open issue in Vite repo: https://github.com/vitejs/vite/issues/7576. Looks like the problem is the same.