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.

Extraneous packages after npm install

See original GitHub issue

Followup to https://github.com/SAP/ui5-cli/issues/282

Might be related to https://github.com/npm/npm/issues/11189

Potential solution: https://github.com/npm/npm/issues/11189#issuecomment-223770995

Expected Behavior

npm ls passes

Current Behavior

npm ERR! extraneous: ava@2.4.0 ...test\node_modules\@ui5\cli\node_modules\ava
npm ERR! extraneous: coveralls@3.0.9 ...test\node_modules\@ui5\cli\node_modules\coveralls
npm ERR! extraneous: cross-env@6.0.3 ...test\node_modules\@ui5\cli\node_modules\cross-env
npm ERR! extraneous: docdash@1.2.0 ...test\node_modules\@ui5\cli\node_modules\docdash
npm ERR! extraneous: eslint@6.8.0 ...test\node_modules\@ui5\cli\node_modules\eslint
npm ERR! extraneous: eslint-config-google@0.14.0 ...test\node_modules\@ui5\cli\node_modules\eslint-config-google
npm ERR! extraneous: eslint-plugin-jsdoc@15.12.2 ...test\node_modules\@ui5\cli\node_modules\eslint-plugin-jsdoc
npm ERR! extraneous: execa@3.4.0 ...test\node_modules\@ui5\cli\node_modules\execa
npm ERR! extraneous: nyc@14.1.1 ...test\node_modules\@ui5\cli\node_modules\nyc
npm ERR! extraneous: open-cli@5.0.0 ...test\node_modules\@ui5\cli\node_modules\open-cli
npm ERR! extraneous: sinon@7.5.0 ...test\node_modules\@ui5\cli\node_modules\sinon
npm ERR! extraneous: tap-nyan@1.1.0 ...test\node_modules\@ui5\cli\node_modules\tap-nyan
npm ERR! extraneous: tap-xunit@2.4.1 ...test\node_modules\@ui5\cli\node_modules\tap-xunit

Steps to reproduce the issue

npm init empty folder
npm install @ui5/cli --save-dev
npm ls

Context

UI5 Module Version (output of ui5 --version when using the CLI): 1.14.0
Node.js Version: any
npm Version: 6.14.2
OS/Platform: Windows

Affected components (if known)

Issue Analytics

State:
Created 4 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

RandomBytecommented, Mar 17, 2020

The change got implemented into our release script. We’ll see the effect with the next release 👍

1reaction

RandomBytecommented, Mar 17, 2020

So, since we want to have locked devDependencies while working on the UI5 CLI project, we can only remove them from the npm-shrinkwrap.json that is going to be published to the npm registry. I guess we can give this a shot.

During release, after the tests have been executed and the version bump is complete (which creates a commit that should not change the shrinkwrap), we can remove all devDependencies (npm prune --production) and update the shrinkwrap (npm shrinkwrap) right before publishing.

I’ll update our internal release script. This will probably be in place for UI5 CLI v2.0.

Top Results From Across the Web

Node.js : Removing extraneous NPM packages

This command removes "extraneous" packages. If a package name is provided, then only packages matching one of the supplied names are removed.

Extraneous Package when Installed Locally - Stack Overflow

After I had installed it locally i.e. npm install phantomjs , it reported that the package was extraneous. ├─┬ phantomjs@1.9.0-3 extraneous ...

npm-prune

This command removes "extraneous" packages. If a package name is provided, then only packages matching one of the supplied names are removed.

Understanding npm ERR! code extraneous with your npm ...

The npm error extraneous means that there are installed packages in your node_modules/ folder that is not listed on your package.json file. The ......

Manage npm packages - Visual Studio (Windows)

To help identify errors, check the npm Output window when installing the packages, as described previously in this article. For example, if one ......