Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Notify big users of eslint-plugin-node that they may want to switch #100

Open
3 of 7 tasks
voxpelli opened this issue Jun 21, 2023 · 2 comments
Open
3 of 7 tasks

Notify big users of eslint-plugin-node that they may want to switch #100

voxpelli opened this issue Jun 21, 2023 · 2 comments

Comments

@voxpelli
Copy link
Member

voxpelli commented Jun 21, 2023 •
edited by scagood

It can be hard for users of eslint-plugin-node to find out that there's a maintained fork of the project.

I did a search to find out if some large projects were still relying on eslint-plugin-node and found out that yes, there indeed still are, so I created some PR:s to help them out:
voxpelli added a commit to voxpelli/json-server that referenced this issue Aug 13, 2023
@voxpelli
Update linting to latest standard / prettier
38d9c5d 
This uses ESLint 8.x, the maintained `eslint-plugin-n` fork of `eslint-plugin-node` (which I co-maintain), latest `eslint-config-standard` (which I also co-maintain) and drops the no longer needed `eslint-plugin-standard`

See: eslint-community/eslint-plugin-n#100
@voxpelli voxpelli mentioned this issue Aug 13, 2023
Open
voxpelli added a commit to voxpelli/ember.js that referenced this issue Aug 13, 2023
@voxpelli
Use maintained fork of eslint-plugin-node
b538720 
Since it can be hard for users of `eslint-plugin-node` to find out that there's a maintained fork from the official ESLint Community project I'm doing a drive where I'm making PR:s to some projects to raise awareness. See: eslint-community/eslint-plugin-n#100
This was referenced Aug 13, 2023
Merged
Closed
voxpelli added a commit to voxpelli/docs that referenced this issue Aug 13, 2023
@voxpelli
Use correct standard peer dependencies
f5f235c 
Replace `eslint-plugin-node` with the now used official fork `eslint-plugin-n`.

Also update to latest version of `eslint-config-standard` and its peer dependencies.

Since it can be hard for users of `eslint-plugin-node` to find out that there's a maintained fork from the official [ESLint Community project](https://github.com/eslint-community) I'm doing a drive where I'm making PR:s to some projects to raise awareness.

See: eslint-community/eslint-plugin-n#100

Disclaimer: I'm a co-maintainer of both `standard` and `eslint-plugin-n`
@voxpelli voxpelli mentioned this issue Aug 13, 2023
Closed
2 tasks
@voxpelli
Copy link
Member Author

Opened three new PR:s and updated the webpack one after feedback

@aladdin-add
Copy link

aladdin-add commented Jan 29, 2024 •
edited

As of I'm writing, eslint-plugin-node, there is still 3M+ downloads per week in npm.

I was preparing a PR to renovate: renovatebot/renovate#26907. hope it helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@voxpelli @aladdin-add