[Feature]: Decouple the Playground wasm from the website build

[elecmonkey]

Currently Rslint's website builds the wasm in full at build time to serve the Playground, which makes the website build slow and prone to failure. These two can be decoupled — as Rspack's Playground does: the wasm ships inside the published @rspack/browser package, and the Playground loads it from jsDelivr at runtime by the version the user selects. Rslint could do the same, having the Playground fetch the wasm from a CDN, which would additionally let users switch between released versions.

I’d like to know whether the maintainers think this proposal makes sense. Thanks.

Follow: #1589

[fansenze]

Sounds great. We’ve also been planning to improve the playground recently, mainly so that code examples for all rules can display information similar to the ESLint playground.

[elecmonkey]

Sounds great. We’ve also been planning to improve the playground recently, mainly so that code examples for all rules can display information similar to the ESLint playground.

Thanks for reply. If there’s anything I can do to help please let me know.