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 releasesv3.10.1 andv3.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 yournode_modules folder could cause all manner of mischief, from crashes to emptynpm 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 rannpm 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 ls documentation. (@shvaikalesh)
• e05c0c2iarna/has-unicode#3iarna/has-unicode#4#13084 Correct changelog entry for shrinkwrap lifecycle order. (@SimenB)
• 823994f#13080 Describe usingnpm pack to see a dry run of publication results in thenpm publish documentation. (@laughinghan)

DEPENDENCY UPDATES

• e44d2dbaproba@1.0.4: Documentation updates and minor refactoring. (@iarna)