4 ms·

Try to set npm set progress=false it speeds up installation time. I am also approaching an alternative solution, to put dev deps in another package.json,

by fibo 11y ago

Try to set npm set progress=false it speeds up installation time. I am also approaching an alternative solution, to put dev deps in another package.json, then do something like npm install src/dev where src/dev is a folder that contains a package.json with dev deps only when you are developing.

orf 11y ago
isn't that what devDependencies is for?
- deleted 11y ago
  [deleted]
- nathancahill 11y ago
  "npm install" installs devDependencies too. You can do "npm install --production" to skip them.
untog 11y ago
While progress=false does decrease install time a little, it's still very long. And the output is incredibly verbose - I'm doing something similar to the OP in automating builds of Node apps and npm is easily the biggest headache in the process. BTW, "npm install --production" installs all dependencies but not devDependencies (which you can get by doing "npm install --save-dev <package>"). That way you can separate dev and prod dependencies within the same package.json file. Feels a little backwards that you specify dev on module install but prod on app install. Maybe --production being the default and --dev being an option makes more sense, but that would be one hell of a breaking change.
joshschreuder 11y ago
v3.7.0 of npm [1] fixed the previously submitted performance problem with the progress bar [2]. Which is not to say you are incorrect (as often disabling logging to the console can speed up operations), but for the most part the bug has been fixed. [1] https://github.com/npm/npm/releases/tag/v3.7.0 https://github.com/npm/npm/releases/tag/v3.7.0 [2] https://twitter.com/gavinjoyce/status/691773956144119808 https://twitter.com/gavinjoyce/status/691773956144119808
- STRML 11y ago
  It has not been fixed: I did a series of PRs on this [1] and the most impactful of them was not merged, although a few smaller ones were. @iarna got to the root cause (instead of simply throttling it as I had been doing) but it has not yet been merged into npmlog. [2] 1. https://github.com/npm/npm/issues/11283#issuecomment-175752264 https://github.com/npm/npm/issues/11283#issuecomment-1757522... 2. https://github.com/npm/npmlog/pull/28 https://github.com/npm/npmlog/pull/28
  - joshschreuder 11y ago
    Fair enough, I'm not up with npm's development on a PR level, so I was just going by this line in the changelog: "This has been patched to eliminate that churn, and our testing shows the progress bar as being eliminated as a source of slow down." Apologies for being misleading.
    - STRML 11y ago
      Just to update you - looks like this has finally been released: https://github.com/npm/npm/releases/tag/v3.8.3 https://github.com/npm/npm/releases/tag/v3.8.3
      - joshschreuder 11y ago
        Great, thanks! I'll check it out. Unfortunately I've not had much luck getting pnpm or ied running on Windows due to the symlinking stuff (though the installation portion is super quick), so hopefully the speed improvements here can help lessen the blow a bit.
      - joshschreuder 11y ago
        As an aside, why does npm check-in the node_modules folder into their repo? I was under the impression this was generally considered bad practice, so it seemed weird seeing it done by the package manager itself :)

by fibo 11y ago

orf 11y ago

isn't that what devDependencies is for?

deleted 11y ago
[deleted]
nathancahill 11y ago
"npm install" installs devDependencies too. You can do "npm install --production" to skip them.

untog 11y ago

While progress=false does decrease install time a little, it's still very long. And the output is incredibly verbose - I'm doing something similar to the OP in automating builds of Node apps and npm is easily the biggest headache in the process. BTW, "npm install --production" installs all dependencies but not devDependencies (which you can get by doing "npm install --save-dev <package>"). That way you can separate dev and prod dependencies within the same package.json file. Feels a little backwards that you specify dev on module install but prod on app install. Maybe --production being the default and --dev being an option makes more sense, but that would be one hell of a breaking change.

joshschreuder 11y ago

v3.7.0 of npm [1] fixed the previously submitted performance problem with the progress bar [2]. Which is not to say you are incorrect (as often disabling logging to the console can speed up operations), but for the most part the bug has been fixed. [1] https://github.com/npm/npm/releases/tag/v3.7.0 https://github.com/npm/npm/releases/tag/v3.7.0 [2] https://twitter.com/gavinjoyce/status/691773956144119808 https://twitter.com/gavinjoyce/status/691773956144119808

STRML 11y ago
It has not been fixed: I did a series of PRs on this [1] and the most impactful of them was not merged, although a few smaller ones were. @iarna got to the root cause (instead of simply throttling it as I had been doing) but it has not yet been merged into npmlog. [2] 1. https://github.com/npm/npm/issues/11283#issuecomment-175752264 https://github.com/npm/npm/issues/11283#issuecomment-1757522... 2. https://github.com/npm/npmlog/pull/28 https://github.com/npm/npmlog/pull/28
- joshschreuder 11y ago
  Fair enough, I'm not up with npm's development on a PR level, so I was just going by this line in the changelog: "This has been patched to eliminate that churn, and our testing shows the progress bar as being eliminated as a source of slow down." Apologies for being misleading.
  - STRML 11y ago
    Just to update you - looks like this has finally been released: https://github.com/npm/npm/releases/tag/v3.8.3 https://github.com/npm/npm/releases/tag/v3.8.3
    - joshschreuder 11y ago
      Great, thanks! I'll check it out. Unfortunately I've not had much luck getting pnpm or ied running on Windows due to the symlinking stuff (though the installation portion is super quick), so hopefully the speed improvements here can help lessen the blow a bit.
    - joshschreuder 11y ago
      As an aside, why does npm check-in the node_modules folder into their repo? I was under the impression this was generally considered bad practice, so it seemed weird seeing it done by the package manager itself :)