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.
Given that we had not one, but two updates to our RC this past week, it should come as no surprise that this week's full release is a bit lighter. We have some documentation patches and a couple of bug fixes via dependency updates.
If you haven't yet checked out last week's release, v3.10.0 and the two follow up releases v3.10.1 and v3.10.2, you really should do so. They're the most important releases we've had in quite a while, fixing a bunch of critical bugs (including an issue impacting publishing with Node.js 6.x) and of course, bringing in the new and improved progress bar.
BUM SYMLINKS BURN NO MORE
There's been a bug lurking where broken symlinks in your node_modules folder could cause all manner of mischief, from crashes to empty npm ls results. The intrepid @watilde tracked this down for us.
This addresses the root cause of the outdated crasher we protected against earlier this week in #13115.
This also fixes #9564, the problem where a bad symlink in your global modules would result in an empty result when you ran npm ls -g.
This ALSO likely fixes numerous "Missing argument #1" errors. (But surely not all of them as that's actually just a generic arity and type-validation failure.)
Hello lovely humans,
npm just published its new version 3.10.3.
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.3 (2016-06-23)
Given that we had not one, but two updates to our RC this past week, it should come as no surprise that this week's full release is a bit lighter. We have some documentation patches and a couple of bug fixes via dependency updates.
If you haven't yet checked out last week's release, v3.10.0 and the two follow up releases v3.10.1 and v3.10.2, you really should do so. They're the most important releases we've had in quite a while, fixing a bunch of critical bugs (including an issue impacting publishing with Node.js 6.x) and of course, bringing in the new and improved progress bar.
BUM SYMLINKS BURN NO MORE
There's been a bug lurking where broken symlinks in your
node_modulesfolder could cause all manner of mischief, from crashes to emptynpm lsresults. The intrepid @watilde tracked this down for us.This addresses the root cause of the outdated crasher we protected against earlier this week in #13115.
This also fixes #9564, the problem where a bad symlink in your global modules would result in an empty result when you ran
npm ls -g.This ALSO likely fixes numerous "Missing argument #1" errors. (But surely not all of them as that's actually just a generic arity and type-validation failure.)
ca92ac4npm/read-package-tree#6read-package-tree@5.1.5: Make bad symlinks be non-fatal errors when reading the tree off disk. (@watilde)BETTER UNICODE DETECTION
6c3f7f0has-unicode@2.0.1: Fix unicode detection on a number of Linux distributions. (@Darkhogg) (@gagern)DOCUMENTATION FIXES
b9243ee#13127 Remove extra backtick fromnpm lsdocumentation. (@shvaikalesh)e05c0c2iarna/has-unicode#3 iarna/has-unicode#4 #13084 Correct changelog entry for shrinkwrap lifecycle order. (@SimenB)823994f#13080 Describe usingnpm packto see a dry run of publication results in thenpm publishdocumentation. (@laughinghan)DEPENDENCY UPDATES
e44d2dbaproba@1.0.4: Documentation updates and minor refactoring. (@iarna)The new version differs by 171 commits .
8c646403.10.38a7729aupdate AUTHORS1d8d30edoc: update changelog for 3.10.3ca92ac4code>read-package-tree@5.1.5</code6c3f7f0code>has-unicode@2.0.1</codee44d2dbcode>aproba@1.0.4</codeb9243eedoc: Remove extra backtick from npm-ls docse05c0c2doc: Correct changelog entry for shrinkwrap lifecycle order823994fdoc: npm-publish(1) mentions npm-pack(1)fa7fc613.10.27472d38doc: update changelog for 3.10.26a33b2coutdated: Ensure errors reading the package tree do not crashfbefb86adduser: Disable progress bar76843deadduser: Rewrite custom flow control to use chain7779e9finit: Disable progress barThere are 171 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade