Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

npm upgrade does not upgrade @nrwl/eslint-plugin-nx

See original GitHub issue

Expected Behavior

Running npm run update should update @nrwl/* to 8.7.0

Current Behavior

"@nrwl/eslint-plugin-nx": "8.6.0", is not automatically updated and blocks the upgrade process:

> ng update @nrwl/workspace
Using package manager: 'npm'
Collecting installed dependencies...
Found 94 dependencies.
Fetching dependency metadata from registry...
                  Package "@nrwl/eslint-plugin-nx" has an incompatible peer dependency to "@nrwl/workspace" (requires "8.6.0", would install "8.7.0").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

Context

"@nrwl/cypress": "8.6.0",
 "@nrwl/eslint-plugin-nx": "8.6.0",
 "@nrwl/express": "8.6.0",
 "@nrwl/jest": "8.6.0",
 "@nrwl/node": "8.6.0",
 "@nrwl/workspace": "8.6.0",

Angular CLI: 9.0.0-next.11
Node: 12.9.1
OS: linux x64
Angular: 9.0.0-next.11
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.803.3
@angular-devkit/build-angular     0.803.12
@angular-devkit/build-optimizer   0.803.12
@angular-devkit/build-webpack     0.803.12
@angular-devkit/core              9.0.0-next.11
@angular-devkit/schematics        8.3.3
@angular/cdk                      9.0.0-next.0
@angular/material                 9.0.0-next.0
@ngtools/webpack                  8.3.12
@schematics/angular               8.3.3
@schematics/update                0.900.0-next.11
rxjs                              6.5.3
typescript                        3.6.4
webpack                           4.39.2

Issue Analytics

State:
Created 4 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

jdpearcecommented, Jul 10, 2020

This is fixed for future releases, but if you still have this problem on an older version of workspace, you can monkey patch the package.json in @nrwl/workspace as in the linked PR.

Having said that, we generally expect folks to upgrade via nx migrate. For documentation see here:

https://nx.dev/angular/workspace/update

1reaction

FrozenPandazcommented, May 29, 2020

Hi, sorry about this.

This was mislabeled as stale. We are testing ways to mark not reproducible issues as stale so that we can focus on actionable items but our initial experiment was too broad and unintentionally labeled this issue as stale.

Top Results From Across the Web

@nrwl/eslint-plugin-nx - npm

Nx is a next generation build system with first class monorepo support and powerful integrations. This package is an ESLint plugin for Nx....

Overview - Nx

A plugin containing a collection of recommended ESLint rule configurations wrapped as ESLint plugins and an Nx specific enforce-module-boundaries rule.

How to fix spawn ENAMETOOLONG error nrwl nx workspace

I just ran into the same issue. I did delete the node_modules folder manually, then re-installed everything with npm install. Also found that ......

@nrwl/eslint-plugin-nx - npm Package Health Analysis | Snyk

The npm package @nrwl/eslint-plugin-nx was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as...

Find and fix problems in your JavaScript code - ESLint ...

It doesn't matter if you're writing JavaScript in the browser or on the ... We just pushed ESLint v8.30.0, which is a minor...