-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
[ERR_UNSUPPORTED_ESM_URL_SCHEME] on windows #121
Comments
Hi 👋 I can't reproduce it on a bare nuxt project. Can you provide a lockfile + the package json please ? Or a stackblitz so i can clone it and run it locally |
I've upgraded nuxt-applicationinsights to 0.7.0, which upgraded nitro-applicationinsights to 0.14.2 and everything is working fine now :) |
This is still an issue on Windows, running Node v22.11.0 / npm v10.9.0 and Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:227:11)
at defaultLoad (node:internal/modules/esm/load:109:3)
at ModuleLoader.load (node:internal/modules/esm/loader:666:12)
at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:479:43)
at #createModuleJob (node:internal/modules/esm/loader:503:36)
at #getJobFromResolveResult (node:internal/modules/esm/loader:274:34)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:242:41) {
code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
} |
Indeed, still an issue, but only in build mode, not in dev mode anymore. Here is a repro: https://github.com/ThibaultVlacich/nitro-appinsights-windows
|
I love windows 🙃 ... i'm going to fix it ASAP after Nuxtnation |
I'm going to release it as a minor (0.15) since I removed I'll plan 1.0 with applicationinsights 3 and the usage of opentelemetry |
Environment
Windows + Nuxt 3.14
Reproduction
https://github.com/ThibaultVlacich/nitro-appinsights-windows
Describe the bug
[nuxt] [request error] [unhandled] [500] Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: