Bug 1663028 - rh-nodejs10: 'npm install' fails with Z_DATA_ERROR
Summary: rh-nodejs10: 'npm install' fails with Z_DATA_ERROR
Keywords:
Status: CLOSED DUPLICATE of bug 1677710
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: rh-nodejs10
Version: rh-nodejs10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Zuzana Svetlikova
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-02 18:24 UTC by Jon Dufresne
Modified: 2021-01-14 09:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-25 14:51:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jon Dufresne 2019-01-02 18:24:33 UTC
Note: The component is wrong as rh-nodejs10 doesn't exist as a component.

Description of problem:

After installing the SCL rh-nodejs10, the command `npm install` fails with the error: Z_DATA_ERROR.

Version-Release number of selected component (if applicable):

rh-nodejs10-3.2-2.el7.x86_64


How reproducible:

100%


Steps to Reproduce:
1. Clean working directory with a NPM shrinkwrap file
2. Clean npm cache (npm cache clean -f)
3. Clean `~/.npm` directory
4. Run command `scl enable rh-nodejs10 -- npm install`


Actual results:

npm ERR! code Z_DATA_ERROR
npm ERR! errno -3
npm ERR! invalid distance too far back


Expected results:

Packages installed to node_modules.


Additional info:

As a workaround, the command `npm ci` works.

Comment 1 Zuzana Svetlikova 2019-01-03 12:54:30 UTC
I did not manage to reproduce it. I tried installing packages both from npm repository and locally cloned repo, but it succeeded in both cases.

Comment 2 Jason Cooper 2019-02-12 21:54:31 UTC
I run into the same error, but it's when I run the audit command (scl enable rh-nodejs10 "npm audit") after running "npm install". It only happens in the branch of my project where I have plotly.js as a dependency.

I'm running CentOS 7.6.1810 (Core).

Comment 3 Zuzana Svetlikova 2019-02-25 14:51:53 UTC

*** This bug has been marked as a duplicate of bug 1677710 ***


Note You need to log in before you can comment on or make changes to this bug.