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

Not able to crate app npm ERR! tar.unpack untar error E:\Project\workspaces\NodeJS\npm-cache\recursive-readdir\2.1.0\package.tgz #1427

Closed
ksrimatk opened this issue Jan 22, 2017 · 4 comments

Comments

@ksrimatk
Copy link

If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.

Can you reproduce the problem with latest npm?

Yes
Many errors, especially related to "missing modules", are due to npm bugs.

If you're using Windows, follow these instructions to update npm.

If you're using OS X or Linux, run this to update npm:

npm install -g npm@latest

cd your_project_directory
rm -rf node_modules
npm install

Then try to reproduce the issue again.

Can you still reproduce it?
yes

Description

What are you reporting?
New app is not getting created

Expected behavior

React app needs to be created
Tell us what you think should happen.

Actual behavior

Tell us what actually happens.

ended up with exceptin provided in logs

Environment

Run these commands in the project folder and fill in their results:

  1. npm ls react-scripts (if you haven’t ejected):
    my-new-app@0.1.0 E:\Project\workspaces\NodeJS\react\my-new-app
    `-- (empty)
  2. node -v:
    v6.9.4
  3. npm -v:
    4.1.1

Then, specify:

  1. Operating system:
    Windows 7
  2. Browser and version:
    Chrome

Reproducible Demo

installed latest version of create-react-app then tried creating new app (Ran CMD as admin)

ConsoleLog.zip

@gaearon
Copy link
Contributor

gaearon commented Jan 22, 2017

Could you run npm cache clear and then try again?

@ksrimatk
Copy link
Author

Same result, even I have changed cache location

@gaearon
Copy link
Contributor

gaearon commented Jan 22, 2017

This looks like npm bug but I'm not sure how to consistently reproduce it. Do you see it with npm 3.10.8?

@gaearon
Copy link
Contributor

gaearon commented Jan 22, 2017

Maybe any tips here could help: npm/npm#5133. Could be a no disk space issue, a permissions issue, a network issue, etc. In either case it is a problem with your npm setup.

At the very least I would recommend clearing E:\Project\workspaces\NodeJS\npm-cache\ since that's where the issue occurs. If it doesn't help maybe try to reinstall Node. Unfortunately at this point we are unlikely to help: the issue is clearly with npm. You could also try using Yarn instead (CRA will automatically use it if it's installed globally).

I'm closing because there's not much we can do but I hope this helps.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants