chore(npm): publish artifacts to npm

[btford]

Note that there are still a few pending tasks before this can land, namely getting permissions for all of the package names on npm:

• angular – got it. Thanks @bclinkinbeard!
• angular-animate – got it. thanks @PitBeast!
• angular-cookies – got it. Thanks @petermelias!
• angular-mocks – got it. Thanks @Zizzamia!
• angular-route – got it. Thanks @mljsimone!
• angular-resource – got it. Thanks @roylines!
• angular-sanitize – got it. Thanks @akalinovski!

If you own one of these packages, you can help by adding user "angularcore" to the package

unclaimed:

• angular-aria
• angular-i18n
• angular-loader
• angular-scenario
• angular-touch
• angular-messages

I also still need to add package.json for each bower-angular-* repo (since that's how we'll be publishing these artifacts). done!

Closes #2877

[Zizzamia]

I'm happy to make the name "angular-mocks" for the Angular Team to use.

[btford]

@Zizzamia thanks! Can you give npm user "angularcore" the permissions?

[alexgorbatchev]

👍 thanks @Zizzamia

[roylines]

I am happy to hand over angular-resource. Try and sort it tomorrow.

[mljsimone]

angular-route now belongs to angularcore. Thanks guys!

[lgalfaso]

angular-animate belongs to @PitBeast

[btford]

@lgalfaso good call.

[dylang]

@mljsimone Did we lose older versions of angular-route in this transition? We were using 1.2.12 but it doesn't seem to be available anymore.

Edit: It seems more likely that we had this on our private npm server and it was overwritten when the official package was published. Our issue, not yours. Sorry for any confusion!

[Zizzamia]

Done! :)

[roylines]

I've added angularcore as owner of angular-resource. I've left myself as an owner for the time being (in case of any issues). Feel free to boot me out when you are happy you have necessary ownership rights.

[PitBeast]

I've provide access to angular-sanitize and angular-animate.

[txbm]

I've just transferred ownership of the angular-cookies namespace to angularcore

[btford]

Woo! Should basically be good to go. 💃

[btford]

Landed as a21d49c.

[alexgorbatchev]

Btw, I want to point out the obvious here - it's super cool that everyone gave up their project names for the greater good of the ecosystem. Thanks! 👍

[leon]

@btford Would it be possible to also publish the latest 1.2 releases to npm?

[btford]

We'll publish the next 1.2 release to npm. We can't publish past releases
because some of the packages on npm already have releases published with
those versions.
On Mon Nov 17 2014 at 12:50:23 AM Leon Radley notifications@github.com
wrote:

@btford https://github.com/btford Would it be possible to also publish
the latest 1.2 releases to npm?

—
Reply to this email directly or view it on GitHub
#9376 (comment).

[mgol]

TBH I'm not sure if publishing Angular 1.2 to npm is a good idea. The npm angular package is one provided as a CommonJS module so such a publication would break people that put "angular": "~1.2.0" in their package.json. It's an universally accepted practice in npm to depend on patch updates not introducing any breaking changes, not to mention such a huge package swap.

I don't think there's a safe way to publish Angular 1.2 to npm, it should be left as it is IMO.

[bclinkinbeard]

+1 on @mzgol's comment