You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you may be aware, tslint is going to become deprecated by the end of 2019, and eslint will take over its role. I'm currently working on porting tslint-immutable over to eslint and plan on supporting both TypeScript and vanilla JavaScript in the new version.
As tslint-immutable was originally based on eslint-plugin-immutable, and the tslint version has become a lot more fleshed out and contains a larger community than this project, would you be willing to transfer ownership of the eslint-plugin-immutable npm package name and have our version live on as the successor of this project?
This plugin has three rules, no-let, no-this, and no-mutation. The eslint-plugin-ts-immutable plugin covers these rules and add more rules.
We are now at a point were we need to publish and it would be very nice to have the shorter name of this plugin as it would save some typing when specifying the rules in the config (immutable/* vs ts-immutable/*).
Hey there,
I'm a contributor for
tslint-immutable
.As you may be aware, tslint is going to become deprecated by the end of 2019, and eslint will take over its role. I'm currently working on porting tslint-immutable over to eslint and plan on supporting both TypeScript and vanilla JavaScript in the new version.
As tslint-immutable was originally based on eslint-plugin-immutable, and the tslint version has become a lot more fleshed out and contains a larger community than this project, would you be willing to transfer ownership of the
eslint-plugin-immutable
npm package name and have our version live on as the successor of this project?jonaskello/tslint-immutable/issues/139
The text was updated successfully, but these errors were encountered: