`ERR_UNSUPPORTED_ESM_URL_SCHEME` on Windows

[fdeters]

Issue

Running npx ember-vite-codemod@latest on Windows throws a Node error ERR_UNSUPPORTED_ESM_URL_SCHEME.

Steps to reproduce

1. On Windows, create a new Ember app (I used 6.2.3).
2. Run npx ember-vite-codemod@latest at the project root (I used 0.10.0).
3. Observe error output (identical with or without --error-trace):

$ npx ember-vite-codemod@latest --error-trace
node:internal/errors:496
    ErrorCaptureStackTrace(err);
    ^

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 new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:416:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:287:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:311:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:264:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:250:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:335:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

Node.js v18.19.1

Notes

• I originally observed this when testing it out on an app that uses @embroider/webpack, then got the same error when trying with a fresh classic-build app.

[mansona]

So the good news is that we have been able to recreate the issue in CI 🎉 the bad news is that I'm not exactly sure what is causing the issue 🤔 I'll see if I can get hold of a windows machine soon and try it out

[fdeters]

@mansona I tracked it down to line 4 in lib/utils/get-app-name.js, where process.cwd() is returning a path like C:\path\to\project that is being passed straight to import():

// lib/utils/get-app-name.js

import { join } from 'node:path';

export async function getAppName() {
  const ENV = await import(join(process.cwd(), 'config/environment.js'));
  return ENV.default().modulePrefix;
}

I would accompany this with a PR if I knew anything about how to handle it (sorry)

[fdeters]

Update: I've been able to patch and successfully run the codemod locally by wrapping the ENV import with pathToFileURL:

// lib/utils/get-app-name.js

import { join } from 'node:path';
import { pathToFileURL } from 'node:url';

export async function getAppName() {
  const ENV = await import(
    pathToFileURL(join(process.cwd(), 'config/environment.js'))
  );
  return ENV.default().modulePrefix;
}

I got out of my depth pretty quickly trying to PR it due to mystifying windows CI failures, but the fix has worked for me on multiple apps.

[mansona]

thanks for tracking this down, it's pretty tough to do when you don't have a windows machine easily accessible 😂

I've tried applying your suggestion to #67 and we'll see what CI does