Missing packages after first npm install

Question

Missing packages after first npm install

benoitvallon opened this issue 9 years ago · comments

After the first npm install on my project, some packages are missing. After the second run, all the packages are here. The project is this one react-native-nw-react-calculator

node: v5.3.0
npm: ok with 3.3.9, nok with 3.3.10, still nok with 3.5.3

Here is a sample of the package tree after install, with npm 3.3.9 I got the slash and shebang-regex packages which I don't get with 3.3.10 or the last version (3.5.3)

npm 3.3.9
├-┬ babel-core@6.3.26 
 :  : 
│├── private@0.1.6 
│├── shebang-regex@1.0.0 
│├── slash@1.0.0 
│└── source-map@0.5.3

npm 3.3.10 or 3.5.3
├-┬ babel-core@6.3.26 
 :  :
│├── private@0.1.6 
│└── source-map@0.5.3

I managed to find the commit introducing the bug deps: When we replace/upgrade a dep, remove all its deps too but I am a little stuck to go further and fix the bug.

If anyone could help me with this, I would be happy to fix it.

Benoit VALLON · Answer 1 · Mon Jan 04 2016 22:18:31 GMT+0800 (China Standard Time)

Here are the logs in travis for different version of npm and node https://travis-ci.org/benoitvallon/react-native-nw-react-calculator

We can see that it works great with npm 3.3.6 for example. The behavior appears in 3.3.10 but there is no errors at install, only packages are missing.

hikingyo · Answer 2 · Tue Jan 05 2016 03:36:39 GMT+0800 (China Standard Time)

I have the same problem with npm 3.3.12 on travis and on my own computer.
On my computer, I should to execute several times npm install to have all the packages install.

Benoit VALLON · Answer 3 · Tue Jan 26 2016 23:31:14 GMT+0800 (China Standard Time)

Still having the issue with npm v3.6.0

npm-robot · Answer 4 · Mon Jun 19 2017 18:19:07 GMT+0800 (China Standard Time)

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.