ERR_UNSUPPORTED_ESM_URL_SCHEME
See original GitHub issueEnvironment
- Operating System:
Windows_NT
- Node Version:
v16.15.0
- Nuxt Version:
3.0.0-rc.13-27776700.5a88510
- Nitro Version:
0.6.1-27776717.ed4c0f8
- Package Manager:
yarn@1.22.17
- Builder:
vite
- User Config:
app
,build
,buildModules
,googleFonts
,modules
,routeRules
- Runtime Modules:
@sidebase/nuxt-session@0.2.1
,@nuxtjs/tailwindcss@5.3.5
,@nuxtjs/strapi@1.6.1
,nuxt-icon@0.1.7
- Build Modules:
@nuxtjs/google-fonts@3.0.0-0
Reproduction
No response
Describe the bug
On Windows 11 i have this error
[worker reload] [worker init] Only URLs with a scheme in: file, data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol ‘e:’
Additional context
No response
Logs
WARN
ode_modules@sidebase
untimeserverapisession.get' is imported by virtual:#internal/nitro/virtual/server-handlers, but could not be resolved – treating it as an external dependency
WARN
ode_modules@sidebase
untimeserverapisession.delete' is imported by virtual:#internal/nitro/virtual/server-handlers, but could not be resolved – treating it as an external dependency
WARN
ode_modules@sidebase
untimeservermiddlewaresession' is imported by virtual:#internal/nitro/virtual/server-handlers, but could not be resolved – treating it as an external dependency
WARN
ode_modules@sidebase
untimeserverapisession.patch' is imported by virtual:#internal/nitro/virtual/server-handlers, but could not be resolved – treating it as an external dependency
WARN
ode_modules@sidebase
untimeserverapisession.post' is imported by virtual:#internal/nitro/virtual/server-handlers, but could not be resolved – treating it as an external dependency
√ Nitro built in 501 ms nitro 13:33:21
ERROR [worker reload] [worker init] Only URLs with a scheme in: file, data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'e:'
at new NodeError (node:internal/errors:372:5)
at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1120:11)
at defaultResolve (node:internal/modules/esm/resolve:1200:3)
at ESMLoader.resolve (node:internal/modules/esm/loader:580:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:294:18)
at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:80:40)
at link (node:internal/modules/esm/module_job:78:36)
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file ...
ERROR Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. On Windows, absolute paths must be valid ...
Read more >ERR_UNSUPPORTED_ESM_U...
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. On Windows, absolute paths must be ...
Read more >Lab 7.1 ERR_UNSUPPORTED_ESM_URL_SCHEME
When execting npm test in Lab 7.1 on WIndows 11 with Node v16.14.0 installed I get the following error:
Read more >Only file and data URLs are supported by the default ESM ...
Coding example for the question Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader - Vue 3-Vue.js.
Read more >Running PostCSS - ESM loader Error - support - HUGO
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. Received protocol 'node:' at Loader.
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
@blumgart / @Yan-Thomas we’ll do a release within the next hour that you can then directly use (:
Hi @blumgart!
Thank you for reporting this bug! I opened a new Pull Request (#13) and implemented your changes. Based on my testing the module now works on windows!
You are welcome to clone the repository and test it out yourself!