-
Notifications
You must be signed in to change notification settings - Fork 3
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
Scribe.js does not work using Node.js on Windows #9
Comments
Based on these messages there appears to be some issue specific to running with Node.js on Windows. I'll look into whether it's possible to get it running on Windows without undue effort. |
I investigated this, and it is currently not possible for us to support Node.js for Windows. The error messages you were encountering were caused by the fact that the The most significant issue is that The only thing I can recommend is running a Ubuntu terminal from Windows using WSL2. WSL2 integrates very well with Windows (once installed you just open a different command line), and you won't need to deal with any of Windows-specific issues (which appear to be very common across |
Thanks for the quick resolution. I will do my best |
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:236:11)
at defaultLoad (node:internal/modules/esm/load:128:3)
at ModuleLoader.load (node:internal/modules/esm/loader:409:13)
at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:291:56)
at new ModuleJob (node:internal/modules/esm/module_job:65:26)
at #createModuleJob (node:internal/modules/esm/loader:303:17)
at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:260:34)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:241:17)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ModuleLoader.import (node:internal/modules/esm/loader:328:23) {
code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
The text was updated successfully, but these errors were encountered: