We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
when I run the following testcase in the dockerfile with npm 7.0.6 it fails with:
npm ERR! Cannot read property 'once' of undefined
Running it with 7.0.5 works as expected.
Dockerfile:
FROM ubuntu:20.04 # silence debconf ENV DEBIAN_FRONTEND=noninteractive # update base packages RUN apt-get update && apt-get upgrade -y # install nodejs WORKDIR /opt RUN apt-get install -y tar wget xz-utils RUN wget --no-check-certificate https://nodejs.org/download/release/latest-v12.x/node-v12.19.0-linux-x64.tar.xz \ && tar -axvf node-v12.19.0-linux-x64.tar.xz RUN ln -s /opt/node-v12.19.0-linux-x64/bin/* /usr/local/bin/ # upgrade npm RUN npm install npm@7.0.6 -g # CVE-2020-15095 / GHSA-xgh6-85xh-479p RUN npm --version # run testcase WORKDIR /testcase ADD package.json . RUN npm run testcase
package.json:
{ "name": "testcase", "version": "1.0.0", "description": "dummy test case", "scripts": { "testcase": "/bin/true" } }
Could you please take a look?
The text was updated successfully, but these errors were encountered:
stripped
8d765b4
Issue: npm/cli#2065
For convenience I added both files into a repo: https://github.com/gjasny/2065-npm-error-reproducer
Sorry, something went wrong.
Duplicate of npm/run-script#13. 🙂
i believe this should be fixed in 7.0.7, can you try to update with npm i npm@7 and see if it's resolved for you?
npm i npm@7
@nlf I can confirm that this issue is fixed. Thanks!
nlf
Successfully merging a pull request may close this issue.
Hello,
when I run the following testcase in the dockerfile with npm 7.0.6 it fails with:
Running it with 7.0.5 works as expected.
Dockerfile:
package.json:
Could you please take a look?
The text was updated successfully, but these errors were encountered: