feat: set legacy decorators version when experimentalDecorators enabled

[Timeless0911]

Summary

• use tsconfck to find and parse tsconfig file
• set legacy decorators version when experimentalDecorators enabled
• add tsconfigPath test cases
• prebundle rslog

Related Links

Checklist

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

[netlify]

✅ Deploy Preview for rslib ready!

Name	Link
🔨 Latest commit	9a32c86
🔍 Latest deploy log	https://app.netlify.com/sites/rslib/deploys/66e015d3f913e40008aadb31
😎 Deploy Preview	https://deploy-preview-189--rslib.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 site configuration.

[fi3ework]

I just recalled web-infra-dev/modern.js#5834.

How does esbuild do? See https://github.com/evanw/esbuild/blob/main/CHANGELOG.md#0210:

Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

For projects that have experimentalDecorator enabled in tsconfig, should we automatically switch to legacyDecorator (and emitDecoratorMetadata)? Additionally, when we perform checks between configurations later on, legacyDecorator should also check whether it is compatible with decorators.version.

In create-rslib, I think we're good to use the new version of decorator by default.

[Timeless0911]

https://github.com/web-infra-dev/rsbuild/blob/01a8b34143b4957225186e9b80b050103582e546/packages/core/src/plugins/swc.ts#L250-L273

The Rsbuild logic is above, and we should just do a tsconfig detect, and if users config experimentalDecorator: true, we automatically inject legacy decorator Rsbuild config.

[fi3ework]

web-infra-dev/rsbuild@01a8b34/packages/core/src/plugins/swc.ts#L250-L273

The Rsbuild logic is above, and we should just do a tsconfig detect, and if users config experimentalDecorator: true, we automatically inject legacy decorator Rsbuild config.

Should this be handled by Rsbuild? I think it also applies to app building.

[Timeless0911]

web-infra-dev/rsbuild@01a8b34/packages/core/src/plugins/swc.ts#L250-L273
The Rsbuild logic is above, and we should just do a tsconfig detect, and if users config experimentalDecorator: true, we automatically inject legacy decorator Rsbuild config.

Should this be handled by Rsbuild? I think it also applies to app building.

Rsbuild does not want to be associated with tsconfig.json fields.