Before You File a Proposal Please Confirm You Have Done The Following...

• I have searched for related issues and found none that match my proposal.
• I have searched the current rule list and found no rules that match my proposal.
• I have read the FAQ and my problem is not listed.

Relevant Package

website

My proposal is suitable for this project

• I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

Description

I recently inquired about the Website Playground in #10798. Since then, after more review of the codebase, I believe there is too much application code for us to try and recreate for our own product. While we clearly don't need the whole playground itself, we do need a way to easily execute ESLint+TS ESLint validation over editor contents. This core functionality seems not available in the ecosystem right now, but is achieved on your website. How feasible would it be to have that core distributed on npm for others to consume? I appreciate the fact that I am asking about something which partially implicates an unrelated projects which is ESLint itself, and perhaps its that project which should ideally lead with a browser compatible package. I'm not sure what makes most sense for TS ESLint, but given you already solved this, maybe its not a stretch to publish that solution/tweaked solution for others.

Thanks for any consideration :)
(and great projects thanks all :))

Additional Info

No response