This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of npm.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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.
Yay! Release time! It's a rainy day, and we have another smallish release for y'all. These things are not necessarily related. Or are they 🌧🤔
As far as news go, you may have noticed that the CLI team dropped support fornode@0.12 when that version went out of maintenance. Still, we've avoided explicitly breaking it and node@0.10 so far -- but not much longer.
Sometime soon, the CLI team plans on switching over to language features onlyavailable as of node@4 LTS, and will likely start dropping old versions of node as they go out of maintenance. The new features are exciting! We're really looking forward to using them in the core CLI (and its dependencies) as we keep upwith our current feature work.
And speaking of features, this release is a minor bump due to a small change inhow npm login works for the sake of supporting OAuth-based login for npmEnterprise users. But we won't leave the rest of y'all out -- we're working on a larger version of this feature. Soon enough, you'll be able to log in to npmwith, say, GitHub -- and use some shiny features that come from the integration. Or turn on 2FA and other such security features. Keep your eyes peeled for newon this in the next few releases and our weekly newsletter!
NEW AUTH TYPES
There's a new command line option: --auth-type, which can be used to log in toa supporting registry with OAuth2 or SAML. The current implementation is mainly meant to support npmE customers, so if you're one of those: ask us about using it! If not, just hold off cause we'll have a much more complete version of this feature out soon.
request is pretty heavy. And it loads a bunch of things. It's actually a pretty big chunk of npm's load time. This small patch by Rebecca will make it so npm only loads that module when we're actually intending to make network requests. Those of you who use npm commands that run offline might see a small speedup in startup time.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
npm just published its new version 4.3.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of npm. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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
Yay! Release time! It's a rainy day, and we have another smallish release for y'all. These things are not necessarily related. Or are they🌧 🤔
As far as news go, you may have noticed that the CLI team dropped support for
node@0.12when that version went out of maintenance. Still, we've avoided explicitly breaking it andnode@0.10so far -- but not much longer.Sometime soon, the CLI team plans on switching over to language features onlyavailable as of
node@4 LTS, and will likely start dropping old versions of node as they go out of maintenance. The new features are exciting! We're really looking forward to using them in the core CLI (and its dependencies) as we keep upwith our current feature work.And speaking of features, this release is a minor bump due to a small change inhow
npm loginworks for the sake of supporting OAuth-based login for npmEnterprise users. But we won't leave the rest of y'all out -- we're working on a larger version of this feature. Soon enough, you'll be able to log in to npmwith, say, GitHub -- and use some shiny features that come from the integration. Or turn on 2FA and other such security features. Keep your eyes peeled for newon this in the next few releases and our weekly newsletter!NEW AUTH TYPES
There's a new command line option:
--auth-type, which can be used to log in toa supporting registry with OAuth2 or SAML. The current implementation is mainly meant to support npmE customers, so if you're one of those: ask us about using it! If not, just hold off cause we'll have a much more complete version of this feature out soon.ac8595ebcf2dd89298d2066b61bcdc85de7#13389 Implement single-sign-on support with--auth-typeoption. (@zkat)FASTER STARTUP. SOMETIMES!
requestis pretty heavy. And it loads a bunch of things. It's actually a pretty big chunk of npm's load time. This small patch by Rebecca will make it so npm only loads that module when we're actually intending to make network requests. Those of you who use npm commands that run offline might see a small speedup in startup time.ac73568#15631 Lazy loadcaching-registry-client. (@iarna)DOCUMENTATION
4ad9247#15630 Fix formatting/rendering for root npm README. (@ungoldman)DEPENDENCY UPDATES
8cc1112npm/hosted-git-info#21hosted-git-info@2.2.0: Add support for.tarball()URLs. (@zkat)6eacc1bnpm-registry-mock@1.1.0(@addaleax)a9b6d77aproba@1.1.1(@iarna)The new version differs by 791 commits .
892f5314.3.0788834eupdate AUTHORS87db3f0doc: update changelog for npm@4.3.087f366dcode>aproba@1.1.1</codea1d85becode>hosted-git-info@2.2.0</code3be0168code>npm-registry-mock@1.1.0</coded8ee340test: add tests for oauth and saml support77a0719doc: document new auth options483770dconfig: added new auth-related configs95f5157adduser: add oauth and saml support36541ecadduser: refactor legacy login into its own moduled85d58dnpm: Lazy load caching-registry-client (#15631)6faa462doc: fix readme formatting (#15630)59337204.2.0819b6a6update AUTHORSThere are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.