-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
fix(linter): only depend on eslint v8 #25938
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit f2e274e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
<!-- 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)
Hi @FrozenPandaz |
Does not fully support i guess |
@robertIsaac @astroanu Per the description on this PR, it should work fine to install eslint v9 at the root of your workspace if you want to. This change just fixes the issue that Nx was briefly forcing eslint v9 upon users before they were ready. We are going to look into changing this dependency into a peer dependency in a follow up. It was originally done to keep yarn v1/classic happy I believe |
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
@nx/eslint
is bringing ineslint v9
prematurely.Expected Behavior
@nx/eslint
should not bring ineslint v9
yet. Though, it does have support for havingv9
installed at the workspace level.Related Issue(s)
Fixes #25319