Replace @dual-bundle/import-meta-resolve with import-meta-resolve

[ybiquitous]

In PR #7532, we introduced the @dual-bundle/import-meta-resolve package to support both ESM and CJS, which is a fork of import-meta-resolve that is pure ESM.

When we switch to pure ESM (maybe in the next major version), we can replace @dual-bundle/import-meta-resolve with import-meta-resolve.

See also the code below:

stylelint/lib/utils/resolveSilent.mjs

Lines 6 to 7 in a211d8b

	// TODO: use pure ESM `import-meta-resolve` package in next major version
	import { resolve } from '@dual-bundle/import-meta-resolve';

Note

Node.js has provided the import.meta.resolve() API, and we would like to use the API instead of import-meta-resolve, but it is still experimental. In addition, the --experimental-import-meta-resolve flag is necessary to use the second argument parent (at the point of Node.js 21.7.1). So it may be difficult to switch import.meta.resolve() in the next major version.

[boris-petrov]

Upgrading to Node.js 22.0.0 and running Stylelint leads to (node:202332) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.. It comes from @dual-bundle/import-meta-resolve/lib/resolve.js:139:12. So replacing this package is important to also fix this (if the other one has already resolved that deprecation).

[JounQin]

@boris-petrov I believe you're describing wooorm/import-meta-resolve#27, right?

[boris-petrov]

@JounQin yes. It's good there is an issue so hopefully it will be fixed at some point. :)

[ybiquitous]

https://github.com/wooorm/import-meta-resolve/releases/tag/4.1.0 now resolved the deprecation warning.

@JounQin Could you merge the upstream change into @dual-bundle/import-meta-resolve, please?

[JounQin]

@dual-bundle/import-meta-resolve@4.1.0 has been released.

cc @boris-petrov