Windows support?

[ArjandenHartog]

$ NODE_OPTIONS='--max-old-space-size=8192 --no-deprecation --no-warnings' vinext dev -p 4000
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:195:11)
at defaultLoadSync (node:internal/modules/esm/load:142:3)
at #loadAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:795:12)
at #loadSync (node:internal/modules/esm/loader:815:49)
at ModuleLoader.load (node:internal/modules/esm/loader:780:26)
at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:526:31)
at #getOrCreateModuleJobAfterResolve (node:internal/modules/esm/loader:571:36)
at afterResolve (node:internal/modules/esm/loader:624:52)
at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:630:12)
at onImport.tracePromise.proto (node:internal/modules/esm/loader:649:32) {
code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
error: script "dev" exited with code 1

[niicojs]

#27

[southpolesteve]

Fixed in #31 — the root cause was that all our dynamic import() calls were passing bare Windows absolute paths (C:...) instead of file:// URLs. Node's ESM loader requires file:// URLs on Windows. We wrapped every call site with pathToFileURL() and added a Windows runner to CI for an E2E test so this won't regress. Thanks for reporting this with the clear stack trace, that made it easy to confirm the fix!