RFC: eslint-config-standard-with-typescript to depart from standard

[mightyiam]

Background

eslint-config-standard-with-typescript (-with-typescript) was first published September 2017. Two years later, August 2019, the repository was transferred into the standard organization. We have enjoyed and appreciate the contributions by various members of the community, yet, I and later @rostislav-simonik and @jay-bulk have been the regular contributors since.

Popularity of -with-typescript has been on the rise since the beginning of 2020, with a significant increase in adoption rate since July 2022, which is about the time the mob was formed.

Policy discrepancy

Standard always had a certain approach with regards to the scope and impact of rules and the frequency of releases. And -with-typescript always had quite a different approach. For example, -with-typescript wasn't shy in making frequent major releases that introduced new rules. The reasoning has been that of continuous delivery, semantic commits/releases and the idea that users would be able to bump the version at their own pace.

Suggested solution

-with-typescript will depart from its dependency on eslint-config-standard and therefore depart from its relationship with Standard. This would permit -with-typescript the freedom to introduce such changes that would currently be incompatible with standard. For example, new core ESLint (non-TypeScript) rule.

Of course, We will continue to welcome asynchronous contributions from outside the regular mob sessions.

Co-authored-by: @rostislav-simonik

[wesleytodd]

This makes sense to me. As I have been following things lately I have noticed this is the central tension in the project so I am glad to see there is a way everyone can get what they need/want out of it.

[voxpelli]

I'm 👍 on this, thanks for suggesting 🙏 There are some practicalities to it I guess, so lets sync up on those so that we are all on the same page as to what this would entail.

This is what I'm personally thinking of, from the top of my mind:

• eslint-config-standard-with-typescript, both npm module and repository, will be transferred to the new organization and use existing names as the new org see fit
• ts-standard, both npm module and repository, will be given the same treatment (else deprecated as per https://github.com/standard/ts-standard/issues/291)
• Currently the VSCode support is given through (standard/vscode-standard)[https://github.com/standard/vscode-standard], if the new organization takes on ts-standard, then maybe it wants to have its own copy of standard/vscode-standard as well? To remove dependency on standard/vscode-standard. If so, then such a transition should be assisted with by standard/vscode-standard I think (Thoughts @LinusU, @theoludwig?)

Any other practicalities I'm missing? Any other modules or npm-packages that would need to be moved?

Also: Would the new org still rely on eslint-config-standard or become a self-contained module which copies the current rules over but after that keeps its own maintenance of those? (I think personally this would give the most freedom to the new org)

[mightyiam]

Also: Would the new org still rely on eslint-config-standard or become a self-contained module which copies the current rules over but after that keeps its own maintenance of those? (I think personally this would give the most freedom to the new org)

The latter.

Otherwise, sounds good.

[mightyiam]

@rostislav-simonik and I would like to implement this RFC (depart eslint-config-standard-with-typescript from @standard). We find it reasonable at this point to announce our intention to implement this RFC after a certain future date: 2024-01-12. DMs will be sent to @feross and @mcollina.

[mcollina]

I'm ok with it, +1.

[mightyiam]

The new home is https://github.com/mightyiam/eslint-config-standard-with-typescript .

[mightyiam]

Could someone please make me owner of the eslint-config-standard-with-typescript npm package? @voxpelli perhaps?

[mightyiam]

My npm username is mightyiam.

[voxpelli]

I'm not an admin / owner on npm it seems, ping @LinusU, @bcomnes, @feross

[bcomnes]

Sorry for the delay here. Ok I removed the package eslint-config-standard-with-typescript from the standardjs developers team, and mightyiam and rostislav-simonik remain as maintainers.

Does that look right to everyone?

[mightyiam]

@bcomnes thank you. If the 'maintainer' role means full control, then that seems complete. Could you, perhaps do the same for ts-standard?

[bcomnes]

@mightyiam I tried adding you as a maintainer/collaborator on that package on npm but get a forbidden error. As an admin I am unable to invite you back to the org.

[mightyiam]

@feross perhaps you could? @bcomnes could you perhaps ping some who do have permission to do this?

[voxpelli]

@bcomnes Essentially we should do the same thing with ts-standard as we did with eslint-config-standard-with-typescript and simply give it over to @mightyiam and remove it form the standard organization – on both npm and on GitHub

[bcomnes]

The difference here's that he's no longer on the package as a collaborator, and I'm unable to add outside collaborators as an admin. I think only owners can do this.

[voxpelli]

@bcomnes a problem on both npm and GitHub or just npm?

[bcomnes]

Npm

[voxpelli]

@mightyiam Is this still of interest to solve? If so: Reminder @feross. Else we can close this?

[mightyiam]

ts-standard probably belongs together with eslint-config-standard-with-typescript. I've been making progress there. So, I would say, yes.