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
Can ts-standard use v5.12.1 or higher of @typescript-eslint/parser? #222
Comments
Hey! 👋 We need to add support for ESLint v8 in To do so, there is this PR to update Then the hardest part would be to update The creator/core maintainer of I already suggested to "rewrite" If you want to help, you can try to update |
@divlo - I see that the PR for the newer ESLint is going through some checks now so I will pull it in once accepted. As for @toddbluhm and his activity, would he be able to let others take over? |
I see that there hasn't been an update from @toddbluhm and this project is stuck needing either a rewrite as there are still blockers with this and newer ESLint and TypeScript. Which makes you wonder... why isn't TypeScript integrated with the main standard package? |
Similar to the bottom piece of agilgur5/react-signature-canvas@c70cc5a - I didn't know ts-standard was a thing and had been using eslint-config-standard-with-typescript and all the deps instead before (which itself was a relatively recent development) - I had put off adding ts-standard here to this repo/boilerplate due to its conflicts with `tsc` - I suspect the conflicts are because of ts-standard's old version of ESLint that may not have brought it in sync with the TS developments around index signatures - ts-standard (and the whole standard ecosystem, tbh) have been suffering a bit of lack of maintenance and so have been slow to upgrade etc - for a summary, see standard/ts-standard#222 -- I might just tackle some of the remaining tasks myself? - and as it doesn't seem like it'll be upgraded anytime too soon, figured I might as well bring it in before I put it off for too long - was able to eslint-ignore the 3 conflicts, so think that's good enough as a workaround _for now_ - it doesn't seem to be that much of a problem _within_ some of my other libraries' codebases (as opposed to just in the config), so think it's ok for now unless it starts to pose more problems - remove trailing commas per current ts-standard style - maybe this is changed in newer versions of standard? since trailing commas are better, but may not have been fully supported before - remove `package-json-type` dep as it wasn't helping much and also causing type issues due to custom fields
@btegs I couldn't make this linter work cause this issue is raised to me, do you recommend any kind of workaround? (I'm trying to close this PR attached above as blocked in another project) |
For your information (reference: fastify/fastify-cli#512 (comment)):
|
@mightyiam I thought |
Sounds like an interesting idea and an unrelated discussion. |
UPDATE: I found some free time to rewrite |
As of right now, the version of @typescript-eslint/parser is in the 4.x series, but when I run ts-standard in the command line, I get this warning if I update to a newer version. I would like to use TypeScript 4.5 and above with ts-standard of course:
The text was updated successfully, but these errors were encountered: