feat: Support import.meta.filename/dirname/resolve

[magic-akari]

Summary

• Closes: [Feature]: Support import.meta.resolve + Node Specific Meta Values #8008

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for rspack ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	561581e
🔍 Latest deploy log	https://app.netlify.com/projects/rspack/deploys/6842528a9e59f900083045f4
😎 Deploy Preview	https://deploy-preview-10573--rspack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[codspeed-hq]

CodSpeed Performance Report

Merging #10573 will not alter performance

_{Comparing magic-akari:fix/issue-8008 (561581e) with main (40f964e)}

Summary

✅ 12 untouched benchmarks

[magic-akari]

I haven't yet implemented import.meta.resolve, which provides functionality similar to require.resolve but follows ESM resolution rules.
Since we're currently unsure about the best approach to implement this (and would welcome insights if you have them), I've decided to hold off on implementation for now.

done.

[magic-akari]

On Windows CI, import.meta.url handles file paths differently (using three slashes versus two). Since this PR doesn't address that specific behavior, we'll defer fixing it for now.

- 	expect('file://<TEST_TOOLS_ROOT>/tests/builtinCases/plugin-javascript/import-meta/index.js').toBe(url);
- 	expect('file://<TEST_TOOLS_ROOT>/tests/builtinCases/plugin-javascript/import-meta/index.js').toBe(url);
- 	expect("my" + 'file://<TEST_TOOLS_ROOT>/tests/builtinCases/plugin-javascript/import-meta/index.js').toBe("my" + url);
+ 	expect('file:///<TEST_TOOLS_ROOT>/tests/builtinCases/plugin-javascript/import-meta/index.js').toBe(url);
+ 	expect('file:///<TEST_TOOLS_ROOT>/tests/builtinCases/plugin-javascript/import-meta/index.js').toBe(url);
+ 	expect("my" + 'file:///<TEST_TOOLS_ROOT>/tests/builtinCases/plugin-javascript/import-meta/index.js').toBe("my" + url);

[magic-akari]

It appears that __filename is handled by crates/rspack_plugin_rstest/src/parser_plugin.rs using a different strategy.

[magic-akari]

Using PathBuf::from directly might be more efficient. However, considering that the Resource might contain a query string – which can introduce various edge cases like ./x.js?foo=/../y.js – processing it through a URL parser is safer.

rspack/crates/rspack_loader_runner/src/content.rs

Lines 114 to 115 in 561581e

	/// Resource with absolute path, query and fragment
	pub resource: String,

• ./x.js?foo=/../y.js is resolved as ./y.js instead of ./x.js vitejs/vite#19406