feat(core): add configuration validation using typia

[colinaaa]

Important

Note that this is currently just a POC implementation.

Summary

Add a validation to loadConfig to make sure that the configuration is correct when loaded.

I'm using typia and typia-rspack-plugin to make validation.

1. It use pure TypeScript definition as the source of truth
2. It is fast

Related Links

Checklist

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

[netlify]

✅ Deploy Preview for rslib ready!

Name	Link
🔨 Latest commit	66e1404
🔍 Latest deploy log	https://app.netlify.com/sites/rslib/deploys/67a21d9cf7164b0008abfa07
😎 Deploy Preview	https://deploy-preview-730--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.

[chenjiahan]

typia has so many dependencies, this is a bit hard to accept...

https://pkg-graph.info/typia

[colinaaa]

It indeed has too many dependencies, but it is tree-shakable and we are using it as devDependencies.

The bundle size of Rslib is increased from 106.8 kB to 2484.4 kB. But the size change mainly produced by the validation functions generated by typia:

As you can see, the src/validate.ts has 2.33 MB in stats. And we can make validation opt-in and lazy loaded.

For end users, no additional dependencies need to be installed, and the bundle size of @rslib/core increases by only approximately 2.5 MB.

[chenjiahan]

If we make the validation opt-in, how can users enable the validation?

[colinaaa]

E.g.: if the TypiaRspackPlugin(which transforms src/validation.ts) is commented out, the bundle size of @rslib/core in this PR is only 108.4 kB.

[colinaaa]

If we make the validation opt-in, how can users enable the validation?

Maybe through a environment variable?

// rslib.config.js
process.env['RSLIB_CONFIG_VALIDATION'] = true

export default {}

Or maybe a strictDefineConfig API?

import {strictDefineConfig} from '@rslib/core'

export default strictDefineConfig({})

But I would prefer enabling by default. And opt-out using environment variables.

[chenjiahan]

If it's opt-in, I don't think most users will actively enable it...

If it's opt-out, the performance overhead doesn't seem worth it, we can write code to do some validation manually.

[colinaaa]

Sure, I'm closing this PR. Thank you for your review