feat: reference script modules as URL assets

[chenjiahan]

Summary

If we use new URL() to reference .js or .ts files, they will be treated as URL assets and will not be processed by Rsbuild's built-in swc-loader.

// foo.ts will remain the original content and be output to the dist directory
const fooTs = new URL('./foo.ts', import.meta.url).href;

console.log(fooTs); // "/static/foo.[hash].ts"

Related Links

see #3953

Checklist

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

[netlify]

✅ Deploy Preview for rsbuild ready!

Name	Link
🔨 Latest commit	cc3453f
🔍 Latest deploy log	https://app.netlify.com/sites/rsbuild/deploys/673c239c68891500089767cc
😎 Deploy Preview	https://deploy-preview-4011--rsbuild.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 71 (no change from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

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

[9aoy]

Shall we need to add a guide on how to treat it as a URL asset and have it processed by the built-in swc-loader in Rsbuild?

[chenjiahan]

I have no idea how to support it, do you have any suggestions?

[9aoy]

no idea +1 😢

[chenjiahan]

We can find a solution and include a guide in another PR.