i18n: [NEXT] Crashes on rc.9 and rc.10 `Only file and data URLs are supported by the default ESM loader`
Version
@nuxtjs/i18n: @nuxtjs/i18n@8.0.0-alpha.1-27710980.d1ee9d2
nuxt: 3.0.0-rc.9
Nuxt configuration
Please change to [x] if relevant for this issue:
- Applies to a site deployed to a static server (site generated with
nuxt generate) - Applies to a site deployed to a server with a Node backend
Reproduction Link
I tried updating from rc8 to rc9 today and got the error message below when trying to start in dev mode. Tried deleting .nuxt, node_modules as well as package-lock.json to get a fresh install but it all resulted in the same error. Same story for rc10 and edge rc11.
https://github.com/warflash/nuxt_7426
Steps to reproduce
Clone the repo on windows and run npm run dev
What is Expected?
The instance starts as normal
What is actually happening?
500
Only file and data URLs are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'f:'
at new NodeError (node:internal/errors:371:5)
at defaultResolve (node:internal/modules/esm/resolve:1016:11)
at ESMLoader.resolve (node:internal/modules/esm/loader:422:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:222:40)
at ModuleWrap. (node:internal/modules/esm/module_job:76:40)
at link (node:internal/modules/esm/module_job:75:36)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 16 (6 by maintainers)
Commits related to this issue
- fix: resolve deps modules resolve #1518 resolve #1613 — committed to nuxt-modules/i18n by kazupon 2 years ago
- fix: resolve deps modules (#1653) resolve #1518 resolve #1613 — committed to nuxt-modules/i18n by kazupon 2 years ago
- fix: resolve deps modules (#1653) resolve #1518 resolve #1613 — committed to DarthGigi/i18n by kazupon 2 years ago
I’ve just support import assertions for
import(static). You can try to use with edge version.