-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Lint breaks after updating from 19.0.5 to 19.0.6 #25319
Comments
I have noticed a very similar behaviour:
Worked fine with 19.0.5 but is broken with 19.0.6 and no other changes. |
I experienced the same. Due to this the Update PR is currently on hold |
I have huge performance issue with I think it's the same probleme. I have rollback to 19.0.5. |
Mm.. this isn't much details but I think this might be a separate issue unrelated to this one.
Thank you for reporting it. We'll look into it. |
@Tijawk Please open a fresh issue for your case with maximum information/steps to reproduce |
@JamesHenry Both eslint versions (8.57.x, and 9.x) result in the same error. |
@JamesHenry As you can see no eslint 9 You can see, @nx/eslint@19.0.6 is the culprit, as it references eslint 9! In my package .json there is: So I would say, this way ESLint "sneaks" in there should not be intended! |
with 19.0.5:
With 19.0.6:
And with eslint removed from my package.json (and Nx 19.0.6):
Same error though, still |
When I force eslint to 8.57.0, linting works:
Can someone with npm try this with |
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> ## Current Behavior <!-- This is the behavior we have today --> `@nx/eslint` is bringing in `eslint v9` prematurely. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> `@nx/eslint` should not bring in `eslint v9` yet. Though, it does have support for having `v9` installed at the workspace level. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #25319
👍🏼 |
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> ## Current Behavior <!-- This is the behavior we have today --> `@nx/eslint` is bringing in `eslint v9` prematurely. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> `@nx/eslint` should not bring in `eslint v9` yet. Though, it does have support for having `v9` installed at the workspace level. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #25319 (cherry picked from commit f728058)
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> ## Current Behavior <!-- This is the behavior we have today --> `@nx/eslint` is bringing in `eslint v9` prematurely. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> `@nx/eslint` should not bring in `eslint v9` yet. Though, it does have support for having `v9` installed at the workspace level. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #25319 (cherry picked from commit f728058)
FYI we confirmed this is only an issue with yarn. The other package managers behave how we expected and do not force the eslint v9 dependency upon you. We are still discussing the ultimate resolution to this. |
Can confirm that this is also an issue with pnpm too. Currently on |
@terrymun It's better to open a fresh issue with full context about your specific circumstances, rather than commenting on closed issues. If you are choosing to upgrade from 8 to 9 as your comment suggests then it already confirms it is not directly related to this specific issue. If you open a fresh issue the team will happily take a look |
Current Behavior
After updating to nx 19.0.6, linting will fail inside an angular monorepo. This only ocurres if the user has updated the
@typescript-eslint/*
packages from 7.3.0 to e.g. latest (7.10.0). I guess this has to do with #24632.Expected Behavior
Linting should not break during patch releases.
GitHub Repo
No response
Steps to Reproduce
@typescript-eslint/eslint-plugin
and@typescript-eslint/parser
to 7.10.0Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: