Skip to content
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

[BUG] flood of "npm WARN tar ENOENT: no such file or directory, open [...]" followed by failure #1769

Closed
jasonmay opened this issue Sep 5, 2020 · 2 comments
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release

Comments

@jasonmay
Copy link

jasonmay commented Sep 5, 2020

Current Behavior:

When running a series of install steps I get this error, which doesn't seem specific to the project and more specific to NPM:
image

2020-09-05T13_12_04_167Z-debug.log

Expected Behavior:

I expect all the steps below to exit successfully.

Steps To Reproduce:

  1. Look at [DNM] ENOENT warnings and install failure with local NPM dependencies apollographql/apollo-server#4545.
  2. Clone https://github.com/jasonmay/apollo-server and git fetch && git checkout npm-local-dependency-issue
  3. Follow the steps in the PR and observe the output.

Environment:

  • OS: MacOS 10.15.6
  • Node: 14.6.0
  • npm: 6.14.7
@jasonmay jasonmay added Bug thing that needs fixing Needs Triage needs review for next steps Release 6.x work is associated with a specific npm 6 release labels Sep 5, 2020
@darcyclarke darcyclarke removed the Needs Triage needs review for next steps label Feb 13, 2021
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

1 similar comment
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release
Projects
None yet
Development

No branches or pull requests

2 participants