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

Update npm to version 4.0.5 πŸš€ #1725

Closed
wants to merge 1 commit into from

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

npm just published its new version 4.0.5.

State Update πŸš€
Dependency npm
New version 4.0.5
Type dependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of npm.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


GitHub Release

It's that time of year! December is upon us, which means y'all are just going to be doing a lot less, in general, for the next month or so. The "Xmas Chasm", as we like to call it, has already begun. So for those of you reading it from the other side: Hi! Welcome back!

This week's release is a relatively small one, involving just a few bugfixes and dependency upgrades. The CLI team has been busy recently with scoping out npm@5, and starting to do initial spec work for in-scope stuff.

BUGFIXES

On to the actual changes!

  • 9776d8f #15081 bundledDependencies are intended to be left untouched by the installer, as much as possible -- if they're bundled, we assume that you want to be particular about the contents of your bundle. The installer used to have a corner case where existing dependencies that had bundledDependencies would get clobbered by as the installer moved stuff around, even though the installer already avoided moving deps that were themselves bundled. This is now fixed, along with the connected crasher, and your bundledDeps should be left even more intact than before! (@iarna)
  • fc61c08 #15082 Initialize nodes from bundled dependencies. This should address #14427 and related issues, but it's turned out to be a tremendously difficult issue to reproduce in a test. We decided to include it even pending tests, because we found the root cause of the errors. (@iarna)
  • d8471a2 #12811 Consider devDependencies when deciding whether to hoist a package. This should resolve a variety of missing dependency issues some folks were seeing when devDependencies happened to also be dependencies of your dependencies. This often manifested as modules going missing, or only being installed, after npm install was called twice. (@schmod)

DEPENDENCY UPDATES

  • 5978703 graceful-fs@4.1.11: EPERM errors are Windows are now handled more gracefully. Windows users that tended to see these errors due to, say, an antivirus-induced race condition, should see them much more rarely, if at all. (@isaacs)
  • 85b0174 request@2.79.0 (@simov)
  • 9664d36 tap@8.0.1 (@isaacs)

MISCELLANEOUS


The new version differs by 191 commits .

  • 4d0473c 4.0.5
  • f970fc2 update AUTHORS
  • 04d7c2f doc: update changelog for npm@4.0.5
  • d8471a2 deps: Consider devDependencies when deciding whether to hoist a package
  • fc61c08 inflate-bundled: Initialize nodes from bundled dependencies
  • 868e691 test: Make node tests compatible with windows
  • 744a39b test: Remove network dependency from legacy-optional-deps test
  • db2666d test: Remove network dependency from bearer-token-check test
  • c8a22fe test: Remove network dependency from outdated-symlink test
  • bc32afe test: Remove network dependency from install-test test
  • f0f7b0f dedupe: Remove unused code
  • 9776d8f diff-trees: Stop upgrading adds to moves w/ bundled deps
  • 85b0174 request@2.79.0
  • 9664d36 tap@8.0.1
  • 5978703 graceful-fs@4.1.11

There are 191 commits in total. See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚑ greenkeeper upgrade

@timelf123 timelf123 closed this Feb 4, 2017
@oritpersik oritpersik deleted the greenkeeper-npm-4.0.5 branch June 20, 2017 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants