aboutsummaryrefslogtreecommitdiffstats
path: root/npm-shrinkwrap.json
AgeCommit message (Collapse)Author
2014-03-17chore(shrinkwrap): grunt-jasmine-node is retrieved from githubPeter Bacon Darwin
2014-03-14chore(package.json): update karma to 0.12.0Igor Minar
2014-03-14chore(clean-shrinkwrap): add a utility to clean up the shrinkwrap filePeter Bacon Darwin
This is to deal with https://github.com/npm/npm/issues/3581 See the previous commit for more info. Closes #6672
2014-03-14chore(npm): clean up shrinkwrap file, remove unused propertiesIgor Minar
from our experiements it appears that the presense or absense of the from and resolved properties makes no difference on the behavior of but updates these properties with different values depending on different state of the cache and node_modules. So in order to get clean diffs during updates, we are just going to drop these properties and have a script to do this automatically. Long term this should be fixed in npm: https://github.com/npm/npm/issues/3581
2014-03-13chore(shrinkwrap): update dgeni-packagesPeter Bacon Darwin
2014-03-13chore(shrinkwrap): re-run shrinkwrap locallyPeter Bacon Darwin
This will make the following commit clearer when the update is run.
2014-03-11chore(npm): add shrinkwrap to lock down dependenciesIgor Minar
We need to be able to build angular at older shas, without the lock file / shrinkwrap file the dependencies will resolve differently on different machines and at different times. This will help us avoid broken builds and hard to track down issues. I had to manually edit this file after it was generated because `npm shrinkwrap` will install optional dependencies as if they were hard dependencies. See: https://github.com/npm/npm/issues/2679#issuecomment-37361236 My manual edit: ``` diff --git a/npm-shrinkwrap.json b/npm-shrinkwrap.json index 756df44..dc157eb 100644 --- a/npm-shrinkwrap.json +++ b/npm-shrinkwrap.json @@ -3110,19 +3110,7 @@ "chokidar": { "version": "0.8.1", "from": "https://registry.npmjs.org/chokidar/-/chokidar-0.8.1.tgz", - "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-0.8.1.tgz", - "dependencies": { - "fsevents": { - "version": "0.1.6", - "from": "fsevents@0.1.6", - "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-0.1.6.tgz" - }, - "recursive-readdir": { - "version": "0.0.2", - "from": "recursive-readdir@0.0.2", - "resolved": "https://registry.npmjs.org/recursive-readdir/-/recursive-readdir-0.0.2.tgz" - } - } + "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-0.8.1.tgz" }, "glob": { "version": "3.2.9", ``` Additionally chokidar doesn't list the dependencies above as optional, but that will hopefully be soon fixed: https://github.com/paulmillr/chokidar/pull/106 In the meantime the patch from the PR above needs to be applied to node_modules/karma/node_modules/chokidar/package.json before running `npm shrinkwrap` ---- After this change is applied, angular core developers don't need to do anything differently, except when updating dependencies we need to call `npm update && npm shrinkwrap --dev` followed by reappling my patch above until npm's bug. Closes #6653