Skip to content

fix: change parser peerDep to >=6 #78

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
Oct 5, 2024

Conversation

llimllib
Copy link
Contributor

@llimllib llimllib commented Aug 12, 2024

eslint/parser is now up to version 8, and it seems likely that this plugin will continue working with future versions, so my proposal is just to make the peerDep >= 6.

Alternately, I'd be happy to change it to just add || ^8

(I have done no testing to ensure that version 8 does not actually break anything)

eslint/parser is now up to version 8, and it seems likely that
this plugin will continue working with future versions, so
my proposal is just to make the peerDep >= 6.

Alternately, I'd be happy to change it to just add `|| ^8`
@@ -85,7 +85,7 @@
"typescript": "5.1.6"
},
"peerDependencies": {
"@typescript-eslint/parser": "^6 || ^7",
"@typescript-eslint/parser": ">=6",
Copy link

@c100k c100k Sep 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a maintainer of this package, but as you suggested in the PR description, it's probably better to use || ^8 to avoid any weird behavior with a potential v9 that could break it "silently" in the future.

Besides, I've been testing it on v8 for a while, and it works well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it doesn't seem like this module is in active maintenance, which is why I'd prefer to have >=6 - that at least leaves clients in control of the situation instead of requiring more changes

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(BTW I am not at all trying to shame for it not being actively maintained, I know what I'm paying for it and am glad it's around)

@infctr infctr merged commit b4d0a31 into infctr:master Oct 5, 2024
@infctr
Copy link
Owner

infctr commented Oct 5, 2024

resolves #79

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.

3 participants