Skip to content

Error upgrading past v4.0.3 - eslint-plugin-github should be dependency #165

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

Closed
chadfawcett opened this issue May 1, 2024 · 1 comment · Fixed by #166
Closed

Error upgrading past v4.0.3 - eslint-plugin-github should be dependency #165

chadfawcett opened this issue May 1, 2024 · 1 comment · Fixed by #166
Labels

Comments

@chadfawcett
Copy link
Contributor

Hello! Attempting to update past v4.0.3 results in an error when we run our linter saying eslint-plugin-github couldn't be found. It also points to primer-react/recommended as the spot that's referencing it.

It looks like eslint-plugin-github used to be a dependency AND a devDependency, but was removed from the dependencies in #106.

Since you are using eslint-plugin-github in the published primer plugin, I think it should be a dependency and not a devDependency.

I'm not familiar with the codebase though, so there may be a better explanation. Another option might be to make it a peerDependency.

chadfawcett added a commit to chadfawcett/eslint-plugin-primer-react that referenced this issue May 1, 2024
@joshblack
Copy link
Member

Hey @chadfawcett! Thanks so much for bringing this up, totally agreed too. Not sure how this got removed but it should definitely be a dependency or peerDependency 👍

I'll ask the team to see which one we prefer and respond to the PR that you have open 👀 Thanks again for bringing this up!

joshblack pushed a commit that referenced this issue May 6, 2024
* Move eslint-plugin-github to dependencies

Resolves #165

* Commit package-lock.json changes

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

Successfully merging a pull request may close this issue.

2 participants