-
Notifications
You must be signed in to change notification settings - Fork 40
feat(deps): update deps, support of eslint 8 #38
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR diff size of 26847 lines exceeds the maximum allowed for the inline comments feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR diff size of 26883 lines exceeds the maximum allowed for the inline comments feature.
For what it's worth, I pulled your branch into my current project and it seems to be working as intended. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Please merge! It is the last eslint plugin that does not work under eslint 8. Thanks! |
I know this is not even merged yet, but what's the release schedule here? Can we expect this change to be part of a release in the following days? |
Well considering there hasn't been a release for this in 5 months... I wouldn't count on it happening too quickly haha |
I mean it's understandable since there haven't been any merged PRs since May. Last time there was a PR that was merged, a new patch version was pushed out on the same day. If only there was a way to get @gund's attention... 😊 |
@gund It's totally understandable that you are probably quite busy, but is there any chance you'd be open to people being added as maintainers so that this project isn't left untouched for long periods of time? |
+1 |
Kind of sounds like it might be time for us to ask npm to declare it up for adoption and fork it? Since none of the contributors seem to be active or responsive 🙁 |
While we are waiting for these things to be merged I created a quick and dirty release with this change and #33. Just add the following to your
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR diff size of 26961 lines exceeds the maximum allowed for the inline comments feature.
Published as @delagen/eslint-plugin-deprecation, also included #35 |
Rather than continuing to fork and publish new versions, perhaps the typescript-eslint team would be interested in bringing in this rule. @JamesHenry is there a process for this sort of thing? Is that something the typescript-eslint team would do? Thread TL;DR: |
I updated my previous comment, looks like I'm no longer blocked.
Having said that disclaimer, I'd still like the package to support to support eslint 8, so that we can move forward. Alternatively, it would be awesome to have this rule officially supported by the TypeScript team as @lachieh suggested |
Thanks a lot @Delagen for your work!
But always eslint responds with Could you help me? |
@crystalfp just installed it to try to investigate problem. Seems Eslint support for namespaced plugins is tweaky |
@crystalfp Seems working
What version of ESLINT are you using? |
With your suggestion it works! Now I have to think of a deprecation just to test. |
@@ -1,12 +1,18 @@ | |||
{ | |||
"name": "eslint-plugin-deprecation", | |||
"version": "0.0.0-development", | |||
"name": "@delagen/eslint-plugin-deprecation", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like some of the changes include in this file might not have been intended for the upstream update?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is because of fork. I updated this project in master branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@timgates42 if you has permission to merge and publish npm, I can rebase this Mr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
truncated into #39
It looks like there has been an issue open for a while to add a deprecation rule into the typescript-eslint project. That same issue references another issue that talks about one of three options:
It looks like @gund went down the first route, but given the lack of activity, it might be about time to take a look at implementing the third (implementing a rule based on the tslint implemention). I'll likely have a look at this path over the weekend, but if anyone else wants to take a look, feel free. |
"importHelpers": true, | ||
"sourceMap": true, | ||
"module": "CommonJS", | ||
"target": "ES2015", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if relevant but the change from ES5 to ES2015 is a breaking change :)
ES5 is not ES2015. ES2015 is ES6.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you see supported versions of node.js by eslint, I think it can be even higher
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. I just saw the target change and figured I'd point it out :)
But given that ESLint 8 only supports "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
then I guess it's safe to use ES2019
https://node.green/#ES2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR diff size of 26977 lines exceeds the maximum allowed for the inline comments feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR diff size of 27134 lines exceeds the maximum allowed for the inline comments feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR diff size of 27164 lines exceeds the maximum allowed for the inline comments feature.
Code Climate has analyzed commit 1893daf and detected 0 issues on this pull request. View more on Code Climate. |
Hey folks, this has been resolved in #39! |
Not sure if it correct, but who doesn't make errors?