Split out formatting rules into a separate package

[adidahiya]

Following up on my comments here: #3395 (comment)

I'd like to separate these rules and disable them in the tslint:recommended configuration so that it's easier to use prettier with tslint. Prettier does a great job of formatting and I'd rather invest time & energy in other tslint rules that are not formatting-related.

[ajafff]

That means you want to publish a separate npm package like @tslint/formatting? Are these rules maintained in a separate repo or is this one converted to a monorepo?

Btw. if you want to publish packages with @tslint scope on npm: I accidentally registered that org and would hand it over to you.

[adidahiya]

I'd like to convert this to a monorepo; I think tracking all issues together in one repo is a good workflow we should retain.

Thanks for the offer about the @tslint scope -- I haven't decided if we should use scoped packages or use names like tslint-core, tslint-formatting, etc... but it's certainly worth considering (we'll avoid conflicts if we use the scope).

[JoshuaKGoldberg]

💀 It's time! 💀

TSLint is being deprecated and no longer accepting pull requests for major new changes or features. See #4534. 😱

If you'd like to see this change implemented, you have two choices:

• Recommended: Check if this is available in ESLint + typescript-eslint ✅
• Not Recommended: Fork TSLint locally 🤷‍♂️

👋 It was a pleasure open sourcing with you!

If you believe this message was posted here in error, please comment so we can re-open the issue!