Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
We have a twee little release this week as we come back from the holidays.
0.12 IS UNSUPPORTED NOW (really)
After jumping the gun a little, we can now officially remove 0.12 from our supported versions list. The Node.js project has now officially ended even maintenance support for 0.12 and thus, so will we. To reiterate from the last time we did this:
What this means:
- Your contributions will no longer block on the tests passing on 0.12.
- We will no longer block dependency upgrades on working with 0.12.
- Bugs filed on the npm CLI that are due to incompatibilities with 0.12 (and older versions) will be closed with a strong urging to upgrade to a supported version of Node.
- On the flip side, we'll continue to (happily!) accept patches that address regressions seen when running the CLI with Node.js 0.12.
What this doesn't mean:
- The CLI is going to start depending on ES2015+ features. npm continues to work, in almost all cases, all the way back to Node.js 0.8, and our long history of backwards compatibility is a source of pride for the team.
- We aren't concerned about the problems of users who, for whatever reason, can't update to newer versions of npm. As mentioned above, we're happy to take community patches intended to address regressions.
We're not super interested in taking sides on what version of Node.js you "should" be running. We're a workflow tool, and we understand that you all have a diverse set of operational environments you need to be able to support. At the same time, we are a small team, and we need to put some limits on what we support. Tracking what's supported by our runtime's own team seems most practical, so that's what we're doing.
WRITING TO SYMLINKED
package.json (AND OTHER FILES)
.npmrc were a symlink and you used an
npm command that modified one of these (eg
npm config set or
npm install --save) then previously we would have removed your symlink and replaced it with an ordinary file. While making these files symlinks is pretty uncommon, this was still surprising behavior. With this fix we now overwrite the destination of the symlink and preserve the symlink itself.
email@example.com: When the target is a symlink, write-file-atomic now overwrites the destination of the symlink, instead of replacing the symlink itself. This makes it's behavior match
Fixed a bug where it would ALWAYS fs.stat to look up default mode and chown values even if you'd passed them in. (It still used the values you passed in, but did a needless stat.) (@iarna)
firstname.lastname@example.org: Improvements to how Python is located. New
--devdirflag. (@bnoordhuis) (@mhart)
JSONStream@1.3.0: Add new emitPath option. (@nathanwills)