This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Please publish AngularJS as an NPM module #2877
Description
It just takes a few minutes to publish an npm module of the existing AngularJS project, but it would accomplish the following:
- Enable deployment from the standard infrastructure being used for both server and client Javascript code
- Enable browserify users like me to package up client side libraries I fetch with npm (though in production, I reference a copy on the CDN)
- Find new Angular releases using npm outdated.
- Jump ahead of jQuery, which is in the process of taking over the npm management of their library: Publish the updates to NPM & Setup Travis HorseAJ86/node-jquery#56
The npm name angularjs remains available. I recommend mapping it to git://github.com/angular/angular.js.git#v1.0.x and perhaps also creating an angularjs-unstable which pulls from master.
Thanks!
Activity
darvin commentedon Jun 5, 2013
+1 im using https://github.com/darvin/angular-browserify currently
vizo commentedon Jul 29, 2013
+1
RWOverdijk commentedon Sep 25, 2013
+1.
Or use napa. Works well for me:
npm i napa --save-devand add to package.json:
{ "scripts": { "install": "napa angular/bower-angular:angular" } }bpierre commentedon Sep 26, 2013
The name
angularjs, defined in the package.json, has been taken on npm by this module: https://github.com/eugeneware/angularjseugeneware commentedon Sep 27, 2013
The intention was to have a browserify friendly way to include angularjs, so very happy to give up the name for an officially supported version.
NickHeiner commentedon Oct 3, 2013
👍
seanhess commentedon Oct 9, 2013
+1
aderuwe commentedon Oct 15, 2013
👍
bclinkinbeard commentedon Nov 25, 2013
In the meantime you can use https://npmjs.org/package/angular. It allows you to use Angular from both Browserify and Node directly.
vilmosioo commentedon Nov 27, 2013
+1
steffenmllr commentedon Dec 4, 2013
+1
psi-4ward commentedon Dec 16, 2013
+1
something official would be nice
dcartertwo commentedon Jan 11, 2014
+1. would be great to have something official for angular and its core modules.
xseignard commentedon Jan 11, 2014
i would say +1 too!
dylang commentedon Jan 21, 2014
I asked @bradlygreen about publishing npmjs at #ng-conf and he said they haven't done it yet because it's not necessary for the way Angular is used within Google, but suggested that adding a pull request to the build scripts could help this happen.
I think these are the tasks required, but there could be more:
angular.npm-angular.npm-angularrepo or make changes to the current repo.angularmodule on npm with theangularuser, and/or @eugeneware and yourangularjsmodule.What else is missing and who wants to help?
64 remaining items
chore(npm): publish artifacts to npm
mljsimone commentedon Oct 2, 2014
Yay! +1
jblaise commentedon Oct 3, 2014
nice 👍
mgol commentedon Oct 4, 2014
Note for the future: before a final version is released I guess the publishing command should be like:
Otherwise it'll get tagged as
latestand all people doingnpm install angularwill install the unstable one.This may not be important here since this will be the first official publish anyway.
chore(npm): publish artifacts to npm
btford commentedon Oct 6, 2014
Landed the change to the script, but we'll need to do another release to get the artifacts up.
addyosmani commentedon Oct 6, 2014
Yay. Nice work @btford!
RichardLitt commentedon Oct 7, 2014
👍 Thanks man!
aderuwe commentedon Oct 7, 2014
👍 Awesome!
tanx commentedon Oct 7, 2014
Thanks!
jblaise commentedon Oct 9, 2014
👍 thanks
chore(npm): publish artifacts to npm
seadb commentedon Oct 19, 2015
thank you!