"Fossies" - the Fresh Open Source Software Archive

Member "Atom/resources/app/apm/node_modules/npm/changelogs/CHANGELOG-1.md" (8 Mar 2017, 38254 Bytes) of package /windows/misc/atom-windows.zip:

As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format). Alternatively you can here view or download the uninterpreted source code file. A member file download can also be achieved by clicking within a package contents listing on the according byte size field.

v1.4.29 (2015-10-29):


In a special one-off release as part of the strategy to get a version of npm into Node LTS that works with the current registry, modify npm to print out this deprecation banner literally every time npm is invoked to do anything:

npm WARN deprecated This version of npm lacks support for important features,
npm WARN deprecated such as scoped packages, offered by the primary npm
npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
npm WARN deprecated latest stable version. To upgrade to npm@2, run:
npm WARN deprecated
npm WARN deprecated   npm -g install npm@latest-2
npm WARN deprecated
npm WARN deprecated To upgrade to the latest stable version, run:
npm WARN deprecated
npm WARN deprecated   npm -g install npm@latest
npm WARN deprecated
npm WARN deprecated (Depending on how Node.js was installed on your system, you
npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
npm WARN deprecated on Windows, run them from an Administrator prompt.)
npm WARN deprecated
npm WARN deprecated If you're running the version of npm bundled with
npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
npm WARN deprecated will be bundled with a version of npm@2, which has some small
npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
npm WARN deprecated semver behavior.

The message basically tells the tale: Node 0.10 will finally be getting npm@2, so those of you who haven't upgraded your build systems to deal with its (relatively small) breaking changes should do so now.

Also, this version doesn't even pretend that it can deal with scoped packages, which, given the confusing behavior of older versions of npm@1.4, where it would sometimes try to install packages from GitHub, is a distinct improvement.

There is no good reason for you as an end user to upgrade to this version of npm yourself.

v1.5.0-alpha-4 (2014-07-18):

v1.5.0-alpha-3 (2014-07-17):

v1.5.0-alpha-2 (2014-07-01):

v1.5.0-alpha-1 (2014-07-01):

v1.5.0-alpha-0 (2014-07-01):

v1.4.28 (2014-09-12):

v1.4.27 (2014-09-04):

v1.4.26 (2014-08-28):

v1.4.25 (2014-08-21):

v1.4.24 (2014-08-14):

v1.4.23 (2014-07-31):

v1.4.22 (2014-07-31):

v1.4.21 (2014-07-14):

v1.4.20 (2014-07-02):

v1.4.19 (2014-07-01):

v1.4.18 (2014-06-29):

v1.4.17 (2014-06-27):

v1.2.8000 (2014-06-17):

v1.4.16 (2014-06-17):

v1.4.15 (2014-06-10):

v1.4.14 (2014-06-05):

v1.4.13 (2014-05-23):

v1.4.12 (2014-05-23):

v1.4.11 (2014-05-22):

v1.4.10 (2014-05-05):

v1.4.9 (2014-05-01):

v1.4.8 (2014-05-01):

v1.4.7 (2014-04-15):

v1.4.6 (2014-03-19):

v1.4.5 (2014-03-18):

v1.4.4 (2014-02-20):

v1.4.3 (2014-02-16):

v1.4.2 (2014-02-13):

v1.4.1 (2014-02-13):

v1.4.0 (2014-02-12):

v1.3.26 (2014-02-02):

v1.3.25 (2014-01-25):

v1.3.24 (2014-01-19):

Dependency updates: * 909cccf read-package-json@1.1.6 * a3891b6 rimraf@2.2.6 * ac6efbc sha@1.2.3 * dd30038 node-gyp@0.12.2 * c8c3ebe npm-registry-client@0.3.3 * 4315286 npmconf@0.1.12

v1.3.23 (2014-01-03):

v1.3.22 (2013-12-25):

v1.3.21 (2013-12-17):

v1.3.20 (2013-12-17):

v1.3.19 (2013-12-16):

v1.3.18 (2013-12-16):

v1.3.17 (2013-12-11):

v1.3.16 (2013-12-11):