mlly throws `[error] The URL must be of scheme file` when called with absolute path on windows

[danielroe]

Environment

windows
mlly 1.7.3

Reproduction

danielroe/windows-reproductions#1

Describe the bug

When called with an absolute path on Windows, resolvePathSync fails.

Sample code:

import { dirname, resolve } from 'node:path'
import { fileURLToPath } from 'node:url'

import { resolvePathSync } from 'mlly'

resolvePathSync(
  resolve(fileURLToPath(import.meta.url), '../plugins/router'))
  { extensions: ['.ts', '.js'] }
)

full reproduction

Additional context

originally encountered in nuxt/nuxt#30540

Logs

No response

[pi0]

Node.js ESM resolve requires that Windows absolute paths (same limit of imports) have file proto.

I think for resolvePathSync wrapper we could identify windows absolute paths and do renormalization to avoid this issue.

[mrginglymus]

For reference, upstream bug in wooorm/import-meta-resolve#31

[husayt]

I am getting this error with nuxt-content-meta
nuxt-content/nuxt-component-meta#72 (comment)

[pi0]

Any new dependency should migrate to unjs/exsolve

[husayt]

@danielroe i think i found the culprit. what do you think?
that last line is seems to be causing the exception:
node_modules/.pnpm/nuxt@4.2.2_@parcel+watcher@_65eb2844e3ce3b6edff4711cc93edc90/node_modules/nuxt/dist/app/components/nuxt-link