Skip to content

Mention to eslint-plugin-n #355

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.

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

Merged
merged 1 commit into from
Mar 9, 2024
Merged

Mention to eslint-plugin-n #355

merged 1 commit into from
Mar 9, 2024

Conversation

sosukesuzuki
Copy link
Collaborator

@JounQin
Copy link

JounQin commented May 1, 2025

So I'm curious why we're rebranding if anyone has the permission to publish eslint-plugin-node. The plugin-n is bad name actually which is not clear based on the discussion at un-ts/eslint-plugin-import-x#24 (comment).

cc @sosukesuzuki @ota-meshi @mysticatea

@sosukesuzuki
Copy link
Collaborator Author

I have the permission to write to the GitHub repo, but I don't have the permission to publish to the npm package

@JounQin
Copy link

JounQin commented May 1, 2025

I have the permission to write to the GitHub repo, but I don't have the permission to publish to the npm package

That's unfortunate, @mysticatea .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants