You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am seeing an issue when importing a custom template on windows.
$ swagger-typescript-api -p http://localhost:5005/swagger/v1/swagger.json -o ./src -n api.ts --module-name-index 1 --custom-config custom-config.cjs -t ./templates
Error loading custom config 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 'm:'
at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:239:11)
at defaultLoad (node:internal/modules/esm/load:130:3)
at ModuleLoader.load (node:internal/modules/esm/loader:403:13)
at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:285:56)
at new ModuleJob (node:internal/modules/esm/module_job:67:26)
at #createModuleJob (node:internal/modules/esm/loader:297:17)
at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:254:34)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:235:17)
at async ModuleLoader.import (node:internal/modules/esm/loader:322:23) {
code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
in this case the external drive is named m: and what I believe is causing the problem. It does not know how to load the file correctly. When running the same command from my linux machine with the same structure everything runs successfully. I believe this import approach will resolve the issue. I am happy to make a PR for this fix if preferred.
The text was updated successfully, but these errors were encountered:
Hello, I am seeing an issue when importing a custom template on windows.
in this case the external drive is named m: and what I believe is causing the problem. It does not know how to load the file correctly. When running the same command from my linux machine with the same structure everything runs successfully. I believe this import approach will resolve the issue. I am happy to make a PR for this fix if preferred.
The text was updated successfully, but these errors were encountered: