Lightrun
question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Packages have too many files in them.

See original GitHub issue

Starting at node-pre-gyp 0.8.0, package files are bloated. This behavior didn’t occur with the previously published node-pre-gyp package, 0.7.0. The packages contain many irrelevant files for their target platform. For instance, you can download a package built with node-pre-gyp 0.8.0.

This is the last package that node-pre-gyp created in our build sequence, and it contains the following listed files. If you look at all of the produced packages, it seems fairly obvious that each previous build is being aggregated into the next build’s package.

-rwxr-xr-x  0 0      0     2649912 Mar 20 14:31 electron-v1.0-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2896120 Mar 20 14:37 electron-v1.0-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2649912 Mar 20 14:31 electron-v1.1-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2896120 Mar 20 14:37 electron-v1.1-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2649912 Mar 20 14:32 electron-v1.2-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2896120 Mar 20 14:38 electron-v1.2-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2649936 Mar 20 14:32 electron-v1.3-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2896152 Mar 20 14:38 electron-v1.3-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2649936 Mar 20 14:33 electron-v1.4-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2896152 Mar 20 14:39 electron-v1.4-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2649936 Mar 20 14:33 electron-v1.5-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2896152 Mar 20 14:39 electron-v1.5-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2649936 Mar 20 14:34 electron-v1.6-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2896152 Mar 20 14:40 electron-v1.6-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2649936 Mar 20 14:34 electron-v1.7-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2896152 Mar 20 14:40 electron-v1.7-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2649936 Mar 20 14:35 electron-v1.8-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     2896152 Mar 20 14:41 electron-v1.8-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1269496 Mar 20 14:29 node-v46-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1349364 Mar 20 14:35 node-v46-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1269496 Mar 20 14:29 node-v47-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1349364 Mar 20 14:35 node-v47-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1269496 Mar 20 14:29 node-v48-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1349364 Mar 20 14:35 node-v48-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1269544 Mar 20 14:29 node-v51-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1349412 Mar 20 14:36 node-v51-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1269544 Mar 20 14:30 node-v57-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1349412 Mar 20 14:36 node-v57-darwin-x64-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1270140 Mar 20 14:30 node-v59-darwin-ia32-unknown/grpc_node.node
-rwxr-xr-x  0 0      0     1350044 Mar 20 14:36 node-v59-darwin-x64-unknown/grpc_node.node

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:8 (6 by maintainers)

github_iconTop GitHub Comments

2reactions
springmeyercommented, Apr 28, 2018

should be fixed by #371

0reactions
springmeyercommented, Apr 22, 2018

@agathver perhaps, or perhaps it is the extra from = path.dirname(from); that came in with bb3bdae at https://github.com/mapbox/node-pre-gyp/commit/bb3bdaed56d6540bdd9519f2dbcfdd27d99ed22e#diff-8eaf344b0d37588331d22edb952ddd05R33?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Distributed packages include too many files · Issue #71 - GitHub
By including files that the distributed package does not need, these negative side effects occur: Installs take longer because unneeded ...
Read more >
How to Fix the 'Too Many Open Files' Error in Linux?
It means that a process has opened too many files (file descriptors) and cannot open new ones. On Linux, the “max open file...
Read more >
Why do Java sources have so many folders inside each other?
In large projects, so many packages/libraries are used and in order not to put source files into same folder with another library, programmers...
Read more >
Too many open files - CloudBees Support
You have received an error in the Jenkins application which contains Too many open files in the stacktrace. Example: Caused by: java.io.
Read more >
Why does npm add so many folders to the node_modules ...
When we install a single plugin e.g. gulp-concat, npm installs a bunch of other folders in the node_modules folder. 163 extra folders in...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

node-gyp failure with npm 5.8.0

Next page

Crash build