Joomla! Issue Tracker - CMS

Download
Launch
Feeling Lucky

[#47679] - [6.2] npm fails on windows

No Code Attached Yet bug
avatar brianteeman
brianteeman
24 Apr 2026

What happened?

  1. npm ci fails

Version

6.2

Expected result

npm completes successfully

Actual result

npm fails imediately with


PS D:\repos\j61> npm i

> joomla@6.2.0 install
> node --env-file=./build/production.env build/build.mjs build -a

node:internal/modules/esm/load:209
    throw new ERR_UNSUPPORTED_ESM_URL_SCHEME(parsed, schemes);
          ^

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 'd:'
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:209:11)
    at defaultLoad (node:internal/modules/esm/load:107:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:701:12)
    at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:514:43)
    at #createModuleJob (node:internal/modules/esm/loader:538:36)
    at #getJobFromResolveResult (node:internal/modules/esm/loader:306:34)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:274:41)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:577:25) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

Node.js v22.14.0
npm error code 1
npm error path D:\repos\j61
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c node --env-file=./build/production.env build/build.mjs build -a
npm error A complete log of this run can be found in: C:\Users\brian\AppData\Local\npm-cache\_logs\2026-04-24T07_29_20_011Z-debug-0.log

System Information

Windows 11

Additional Comments

log file extract


51 silly packumentCache corgi:https://registry.npmjs.org/joomla-cypress set size:26202 disposed:false
52 verbose stack Error: command failed
52 verbose stack     at promiseSpawn (C:\Users\brian\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\promise-spawn\lib\index.js:22:22)
52 verbose stack     at spawnWithShell (C:\Users\brian\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\promise-spawn\lib\index.js:124:10)
52 verbose stack     at promiseSpawn (C:\Users\brian\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\promise-spawn\lib\index.js:12:12)
52 verbose stack     at runScriptPkg (C:\Users\brian\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\run-script\lib\run-script-pkg.js:79:13)
52 verbose stack     at runScript (C:\Users\brian\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\run-script\lib\run-script.js:12:10)
52 verbose stack     at async Install.exec (C:\Users\brian\AppData\Roaming\npm\node_modules\npm\lib\commands\install.js:163:9)
52 verbose stack     at async Npm.exec (C:\Users\brian\AppData\Roaming\npm\node_modules\npm\lib\npm.js:208:9)
52 verbose stack     at async module.exports (C:\Users\brian\AppData\Roaming\npm\node_modules\npm\lib\cli\entry.js:67:5)
53 verbose pkgid joomla@6.2.0
54 error code 1
55 error path D:\repos\j61
56 error command failed
57 error command C:\WINDOWS\system32\cmd.exe /d /s /c node --env-file=./build/production.env build/build.mjs build -a
avatar brianteeman brianteeman - open - 24 Apr 2026
avatar joomla-cms-bot joomla-cms-bot - change - 24 Apr 2026
Labels Added: No Code Attached Yet bug
avatar joomla-cms-bot joomla-cms-bot - labeled - 24 Apr 2026
avatar brianteeman
brianteeman - comment - 24 Apr 2026

probably a result of #46879

avatar CSGoat0
CSGoat0 - comment - 24 Apr 2026

The same issue here on windows 10.

avatar Fedik
Fedik - comment - 24 Apr 2026

I think it is because an older node version, not windows

avatar Fedik
Fedik - comment - 24 Apr 2026

Need to update min node requirement in packge.json
To version with support of ESM, i do not remember which it is

avatar brianteeman
brianteeman - comment - 24 Apr 2026 
PS D:\repos\j61> node -v
v22.14.0
avatar brianteeman
brianteeman - comment - 24 Apr 2026

after updating node to the latest release there is no change


PS D:\repos\j61> node -v
v24.15.0
PS D:\repos\j61> npm ci

> joomla@6.2.0 install
> node --env-file=./build/production.env build/build.mjs build -a

node:internal/modules/esm/load:195
    throw new ERR_UNSUPPORTED_ESM_URL_SCHEME(parsed, schemes);
          ^

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 'd:'
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:195:11)
    at defaultLoadSync (node:internal/modules/esm/load:142:3)
    at #loadAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:776:12)
    at #loadSync (node:internal/modules/esm/loader:796:49)
    at ModuleLoader.load (node:internal/modules/esm/loader:762:26)
    at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:504:31)
    at #getOrCreateModuleJobAfterResolve (node:internal/modules/esm/loader:555:36)
    at afterResolve (node:internal/modules/esm/loader:603:52)
    at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:609:12)
    at node:internal/modules/esm/loader:628:32 {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

Node.js v24.15.0
npm error code 1
npm error path D:\repos\j61
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c node --env-file=./build/production.env build/build.mjs build -a
npm error A complete log of this run can be found in: C:\Users\brian\AppData\Local\npm-cache\_logs\2026-04-24T07_57_23_870Z-debug-0.log
avatar Fedik
Fedik - comment - 24 Apr 2026

Thanks for check. That is strange, the trace not realy show anything from build script. I cannot check currently in detail.

Can you please try to run, directly

node build/build.mjs build -a
avatar brianteeman
brianteeman - comment - 24 Apr 2026 
PS D:\repos\j61> node build/build.mjs build -a
node:internal/modules/esm/load:195
    throw new ERR_UNSUPPORTED_ESM_URL_SCHEME(parsed, schemes);
          ^

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 'd:'
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:195:11)
    at defaultLoadSync (node:internal/modules/esm/load:142:3)
    at #loadAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:776:12)
    at #loadSync (node:internal/modules/esm/loader:796:49)
    at ModuleLoader.load (node:internal/modules/esm/loader:762:26)
    at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:504:31)
    at #getOrCreateModuleJobAfterResolve (node:internal/modules/esm/loader:555:36)
    at afterResolve (node:internal/modules/esm/loader:603:52)
    at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:609:12)
    at node:internal/modules/esm/loader:628:32 {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

Node.js v24.15.0
avatar Fedik
Fedik - comment - 24 Apr 2026

Thanks.
Hmhm,

avatar CSGoat0
CSGoat0 - comment - 24 Apr 2026

Someone wrote a solution; It works correctly.
Maybe someone can review and check for technical details.

Add a Comment

Login with GitHub to post a comment