Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
This repository was archived by the owner on Aug 11, 2022. It is now read-only.

v3.4.0

Choose a tag to compare

@iarna iarna released this 13 Nov 01:32

v3.4.0 (2015-11-05):

A NEW FEATURE

This was a group effort, with @isaacs dropping the implementation in back in August. Then, a few days ago, @ashleygwilliams wrote up docs and just today @othiym23 wrote a test.

It's a handy shortcut to update a dependency and then make sure tests still pass.

This new command:

npm install-test x

is the equivalent of running:

npm install x && npm test

BUG FIXES VIA DEPENDENCY UPDATES

  • 31c0080 #8640 npm/normalize-package-data#69 normalize-package-data@2.3.5: Fix a bug where if you didn't specify the name of a scoped module's binary, it would install it such that it was impossible to call it. (@iarna)
  • 02b37bc npm/fstream-npm#14 fstream-npm@1.0.7: Only filter config.gypi when it's in the build directory. (@mscdex)
  • accb9d2 npm/fstream-npm#15 fstream-npm@1.0.6: Stop including directories that happened to have names matching whitelisted npm files in npm module tarballs. The most common cause was that if you had a README directory then everything in it would be included if wanted it or not. (@taion)

DOCUMENTATION FIXES

DEPENDENCY UPDATES FOR THEIR OWN SAKE

Morty Proxy This is a proxified and sanitized view of the page, visit original site.