fix: tentative fix for absolute paths on windows

[mrginglymus]

Given that upstream doesn't want to address this directly (wooorm/import-meta-resolve#31) and downstream is now blocked on this (storybookjs/storybook#32364) here's a tentative workaround for

• fixes mlly throws [error] The URL must be of scheme file when called with absolute path on windows #297

[43081j]

let's wait for @pi0 but i wonder if we should be fixing this at the source instead of the call site

mlly/src/utils.ts

Lines 14 to 19 in e9faaf8

	export function fileURLToPath(id: string | URL): string {
	if (typeof id === "string" && !id.startsWith("file://")) {
	return normalizeSlash(id);
	}
	return normalizeSlash(_fileURLToPath(id));
	}

i feel like maybe this logic should be switcheroo'd?

export function fileURLToPath(id: string | URL): string {
  const idString = typeof id === 'string' ? id : id.href;
  if (id.startsWith("file://")) {
    return normalizeSlash(_fileURLToPath(id)); // pass the original `URL | string` since the built in fileURLToPath accepts both
  }
  return normalizeSlash(idString);
}

[pi0]

Thanks for the PR. I haven't read it through but unlikely we make risky changes in mlly resolve utils anymore as should be deprecated.

I suggest migrating to exsolve and report any windows related issues (i think should be less/no issues with exsolve)

[mrginglymus]

I've raised a PR to migrate to exsolve; however, at this late stage in the release cycle they may be unwilling to switch implementations.

[pi0]

Added two comments on storybookjs/storybook#32383