Importing a worker in ES6 mode fails on Windows:
worker = new Worker(new URL('./worker.js', import.meta.url), {type: 'module'});ends with:
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: 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 'c:'
at new NodeError (node:internal/errors:400:5)
at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1055:11)
at defaultResolve (node:internal/modules/esm/resolve:1135:3)
at nextResolve (node:internal/modules/esm/loader:163:28)
at defer (C:\Users\mmom\src\sqlite-wasm-http\node_modules\ts-node\src\esm.ts:159:23)
at entrypointFallback (C:\Users\mmom\src\sqlite-wasm-http\node_modules\ts-node\src\esm.ts:168:34)
at C:\Users\mmom\src\sqlite-wasm-http\node_modules\ts-node\src\esm.ts:202:16
at addShortCircuitFlag (C:\Users\mmom\src\sqlite-wasm-http\node_modules\ts-node\src\esm.ts:409:21)
at resolve (C:\Users\mmom\src\sqlite-wasm-http\node_modules\ts-node\src\esm.ts:197:12)
at nextResolve (node:internal/modules/esm/loader:163:28) {
code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
The problem is nodejs/node#31710
(yes, initially, mostly everyone is as surprised as I was - but it seems that everyone agrees that this is how it should be)
It comes from this import:
Which happens after removing the file:/// part here:
|
mod = URL.fileURLToPath(new URL.URL(url, baseUrl)); |
Importing a worker in ES6 mode fails on Windows:
ends with:
The problem is nodejs/node#31710
(yes, initially, mostly everyone is as surprised as I was - but it seems that everyone agrees that this is how it should be)
It comes from this import:
web-worker/node.js
Line 178 in 29fef97
Which happens after removing the
file:///part here:web-worker/node.js
Line 101 in 29fef97