This version is covered by your current version range and after updating it in your project the build went from success to failure.
As npm is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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.
This is a quick hotfix release with two small bug fixes. First, there was an issue where the new progress bar would overwrite interactive prompts, that is, those found in npm login and npm init. Second, if the directory you were running npm outdated on was a bad link or otherwise had unrecoverable errors then npm would crash instead of printing the error.
Hello lovely humans,
npm just published its new version 3.10.2.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As npm is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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 :sparkles:
You rock!
:palm_tree:
GitHub Release
v3.10.2 (2016-06-17):
This is a quick hotfix release with two small bug fixes. First, there was an issue where the new progress bar would overwrite interactive prompts, that is, those found in
npm login
andnpm init
. Second, if the directory you were runningnpm outdated
on was a bad link or otherwise had unrecoverable errors then npm would crash instead of printing the error.fbefb86
7779e9f
#13105 Disable progress bar inadduser
andinit
.6a33b2c
#13115 Ensure that errors reading the package tree foroutdated
does not result in crashs. (@iarna)The new version differs by 162 commits .
fa7fc61
3.10.2
7472d38
doc: update changelog for 3.10.2
6a33b2c
outdated: Ensure errors reading the package tree do not crash
fbefb86
adduser: Disable progress bar
76843de
adduser: Rewrite custom flow control to use chain
7779e9f
init: Disable progress bar
7a181fa
3.10.1
b38573f
doc: update changelog for 3.10.1
83e2fed
test: strip trailing comma
1b6ceca
tar: restore our version of applyIgnores
d6afd5f
ci: clean up tested versions
c189723
tar: revert 4e52cef3d4170c8abab98149666ec599
8802f6c
code>fstream@1.0.10</codeef668bd
3.10.0
3b72048
update AUTHORS
There are 162 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade