honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/npm-shrinkwrap.json

22614 lines
1.1 MiB
JSON
Raw Normal View History

chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
{
feat: upgrade clang-format to 1.0.32.
2015-10-20 05:10:31 -04:00
"name": "angular-srcs",
chore(package): update karma-browserstack-launcher to 0.1.7 Closes #5276
2015-11-13 11:09:38 -05:00
"version": "2.0.0-alpha.46",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"angular": {
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"version": "1.4.7",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/angular/-/angular-1.4.7.tgz",
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"resolved": "https://registry.npmjs.org/angular/-/angular-1.4.7.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore: update zone to 0.5.3 Closes #3785
2015-08-21 20:07:31 -04:00
"angular-animate": {
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"version": "1.4.7",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/angular-animate/-/angular-animate-1.4.7.tgz",
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"resolved": "https://registry.npmjs.org/angular-animate/-/angular-animate-1.4.7.tgz"
chore: update zone to 0.5.3 Closes #3785
2015-08-21 20:07:31 -04:00
},
"angular-mocks": {
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"version": "1.4.7",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/angular-mocks/-/angular-mocks-1.4.7.tgz",
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"resolved": "https://registry.npmjs.org/angular-mocks/-/angular-mocks-1.4.7.tgz"
chore: update zone to 0.5.3 Closes #3785
2015-08-21 20:07:31 -04:00
},
chore(npm): Upgrades systemjs to 0.18.3.
2015-08-14 18:05:56 -04:00
"base64-js": {
"version": "0.0.8",
chore(npm): Upgrades systemjs dependency to 0.18.10.
2015-08-17 14:59:49 -04:00
"from": "https://registry.npmjs.org/base64-js/-/base64-js-0.0.8.tgz",
chore(npm): Upgrades systemjs to 0.18.3.
2015-08-14 18:05:56 -04:00
"resolved": "https://registry.npmjs.org/base64-js/-/base64-js-0.0.8.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"bower": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.6.5",
"from": "https://registry.npmjs.org/bower/-/bower-1.6.5.tgz",
"resolved": "https://registry.npmjs.org/bower/-/bower-1.6.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"abbrev": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.7",
"from": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz",
"resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"archy": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/archy/-/archy-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/archy/-/archy-1.0.0.tgz"
},
"bower-config": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.2",
"from": "https://registry.npmjs.org/bower-config/-/bower-config-1.2.2.tgz",
"resolved": "https://registry.npmjs.org/bower-config/-/bower-config-1.2.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"graceful-fs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"optimist": {
"version": "0.6.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
"dependencies": {
"wordwrap": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "0.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"minimist": {
"version": "0.0.10",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz"
}
}
},
"osenv": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.3",
"from": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"dependencies": {
"os-homedir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz"
},
"os-tmpdir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"bower-endpoint-parser": {
"version": "0.2.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/bower-endpoint-parser/-/bower-endpoint-parser-0.2.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/bower-endpoint-parser/-/bower-endpoint-parser-0.2.2.tgz"
},
"bower-json": {
"version": "0.4.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/bower-json/-/bower-json-0.4.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/bower-json/-/bower-json-0.4.0.tgz",
"dependencies": {
"deep-extend": {
"version": "0.2.11",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/deep-extend/-/deep-extend-0.2.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/deep-extend/-/deep-extend-0.2.11.tgz"
},
"graceful-fs": {
"version": "2.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-2.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-2.0.3.tgz"
},
"intersect": {
"version": "0.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/intersect/-/intersect-0.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/intersect/-/intersect-0.0.3.tgz"
}
}
},
"bower-logger": {
"version": "0.2.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/bower-logger/-/bower-logger-0.2.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/bower-logger/-/bower-logger-0.2.2.tgz"
},
"bower-registry-client": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/bower-registry-client/-/bower-registry-client-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/bower-registry-client/-/bower-registry-client-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"async": {
"version": "0.2.10",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
},
"graceful-fs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"request-replay": {
"version": "0.2.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/request-replay/-/request-replay-0.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/request-replay/-/request-replay-0.2.0.tgz"
},
"mkdirp": {
"version": "0.3.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz"
}
}
},
"cardinal": {
"version": "0.4.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/cardinal/-/cardinal-0.4.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/cardinal/-/cardinal-0.4.4.tgz",
"dependencies": {
"redeyed": {
"version": "0.4.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/redeyed/-/redeyed-0.4.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/redeyed/-/redeyed-0.4.4.tgz",
"dependencies": {
"esprima": {
"version": "1.0.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/esprima/-/esprima-1.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/esprima/-/esprima-1.0.4.tgz"
}
}
},
"ansicolors": {
"version": "0.2.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ansicolors/-/ansicolors-0.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ansicolors/-/ansicolors-0.2.1.tgz"
}
}
},
"chalk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-styles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"escape-string-regexp": {
"version": "1.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"supports-color": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"chmodr": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/chmodr/-/chmodr-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/chmodr/-/chmodr-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"configstore": {
"version": "0.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/configstore/-/configstore-0.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/configstore/-/configstore-0.3.2.tgz",
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"js-yaml": {
"version": "3.4.3",
"from": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.3.tgz",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.3.tgz",
"dependencies": {
"argparse": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/argparse/-/argparse-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.2.tgz",
"dependencies": {
"lodash": {
"version": "3.10.1",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
},
"sprintf-js": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz"
}
}
},
"esprima": {
"version": "2.6.0",
"from": "https://registry.npmjs.org/esprima/-/esprima-2.6.0.tgz",
"resolved": "https://registry.npmjs.org/esprima/-/esprima-2.6.0.tgz"
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"object-assign": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-2.1.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-2.1.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"osenv": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.3",
"from": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"dependencies": {
"os-homedir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz"
},
"os-tmpdir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"uuid": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/uuid/-/uuid-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/uuid/-/uuid-2.0.1.tgz"
},
"xdg-basedir": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/xdg-basedir/-/xdg-basedir-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/xdg-basedir/-/xdg-basedir-1.0.1.tgz"
}
}
},
"decompress-zip": {
"version": "0.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/decompress-zip/-/decompress-zip-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/decompress-zip/-/decompress-zip-0.1.0.tgz",
"dependencies": {
"binary": {
"version": "0.3.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/binary/-/binary-0.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/binary/-/binary-0.3.0.tgz",
"dependencies": {
"chainsaw": {
"version": "0.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/chainsaw/-/chainsaw-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/chainsaw/-/chainsaw-0.1.0.tgz",
"dependencies": {
"traverse": {
"version": "0.3.9",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/traverse/-/traverse-0.3.9.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/traverse/-/traverse-0.3.9.tgz"
}
}
},
"buffers": {
"version": "0.1.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/buffers/-/buffers-0.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/buffers/-/buffers-0.1.1.tgz"
}
}
},
"mkpath": {
"version": "0.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mkpath/-/mkpath-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mkpath/-/mkpath-0.1.0.tgz"
},
"readable-stream": {
"version": "1.1.13",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"touch": {
"version": "0.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/touch/-/touch-0.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/touch/-/touch-0.0.3.tgz",
"dependencies": {
"nopt": {
"version": "1.0.10",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/nopt/-/nopt-1.0.10.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/nopt/-/nopt-1.0.10.tgz"
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"destroy": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/destroy/-/destroy-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/destroy/-/destroy-1.0.3.tgz"
},
"fs-write-stream-atomic": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.4",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/fs-write-stream-atomic/-/fs-write-stream-atomic-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/fs-write-stream-atomic/-/fs-write-stream-atomic-1.0.4.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
}
}
},
"fstream": {
"version": "1.0.8",
"from": "https://registry.npmjs.org/fstream/-/fstream-1.0.8.tgz",
"resolved": "https://registry.npmjs.org/fstream/-/fstream-1.0.8.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"fstream-ignore": {
"version": "1.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/fstream-ignore/-/fstream-ignore-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/fstream-ignore/-/fstream-ignore-1.0.2.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"minimatch": {
"version": "2.0.10",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.10.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.10.tgz",
"dependencies": {
"brace-expansion": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"dependencies": {
"balanced-match": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.0.tgz"
},
"concat-map": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
}
}
}
}
}
}
},
"github": {
"version": "0.2.4",
"from": "https://registry.npmjs.org/github/-/github-0.2.4.tgz",
"resolved": "https://registry.npmjs.org/github/-/github-0.2.4.tgz",
"dependencies": {
"mime": {
"version": "1.3.4",
"from": "https://registry.npmjs.org/mime/-/mime-1.3.4.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/mime/-/mime-1.3.4.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glob": {
"version": "4.5.3",
"from": "https://registry.npmjs.org/glob/-/glob-4.5.3.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-4.5.3.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"minimatch": {
"version": "2.0.10",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.10.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.10.tgz",
"dependencies": {
"brace-expansion": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"dependencies": {
"balanced-match": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.0.tgz"
},
"concat-map": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
}
}
}
}
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"graceful-fs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.8",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"handlebars": {
"version": "2.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/handlebars/-/handlebars-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/handlebars/-/handlebars-2.0.0.tgz",
"dependencies": {
"optimist": {
"version": "0.3.7",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/optimist/-/optimist-0.3.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.3.7.tgz",
"dependencies": {
"wordwrap": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "0.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"uglify-js": {
"version": "2.3.6",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.3.6.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.3.6.tgz",
"dependencies": {
"async": {
"version": "0.2.10",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
},
"source-map": {
"version": "0.1.43",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/source-map/-/source-map-0.1.43.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.43.tgz",
"dependencies": {
"amdefine": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
"inquirer": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.10.0",
"from": "https://registry.npmjs.org/inquirer/-/inquirer-0.10.0.tgz",
"resolved": "https://registry.npmjs.org/inquirer/-/inquirer-0.10.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi-escapes": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-1.1.0.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"cli-cursor": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/cli-cursor/-/cli-cursor-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/cli-cursor/-/cli-cursor-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"restore-cursor": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/restore-cursor/-/restore-cursor-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/restore-cursor/-/restore-cursor-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"exit-hook": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/exit-hook/-/exit-hook-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/exit-hook/-/exit-hook-1.1.1.tgz"
},
"onetime": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/onetime/-/onetime-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/onetime/-/onetime-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"cli-width": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/cli-width/-/cli-width-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/cli-width/-/cli-width-1.0.1.tgz"
},
"figures": {
"version": "1.4.0",
"from": "https://registry.npmjs.org/figures/-/figures-1.4.0.tgz",
"resolved": "https://registry.npmjs.org/figures/-/figures-1.4.0.tgz"
},
"lodash": {
"version": "3.10.1",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
},
"readline2": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/readline2/-/readline2-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/readline2/-/readline2-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"code-point-at": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/code-point-at/-/code-point-at-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/code-point-at/-/code-point-at-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-fullwidth-code-point": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"mute-stream": {
"version": "0.0.5",
"from": "https://registry.npmjs.org/mute-stream/-/mute-stream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/mute-stream/-/mute-stream-0.0.5.tgz"
}
}
},
"run-async": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/run-async/-/run-async-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/run-async/-/run-async-0.1.0.tgz",
"dependencies": {
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"rx-lite": {
"version": "3.1.2",
"from": "https://registry.npmjs.org/rx-lite/-/rx-lite-3.1.2.tgz",
"resolved": "https://registry.npmjs.org/rx-lite/-/rx-lite-3.1.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"through": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.3.8",
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"insight": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.7.0",
"from": "https://registry.npmjs.org/insight/-/insight-0.7.0.tgz",
"resolved": "https://registry.npmjs.org/insight/-/insight-0.7.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"async": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.4.2",
"from": "https://registry.npmjs.org/async/-/async-1.4.2.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-1.4.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"configstore": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/configstore/-/configstore-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/configstore/-/configstore-1.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
},
"os-tmpdir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz"
},
"osenv": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"dependencies": {
"os-homedir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz"
}
}
},
"uuid": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/uuid/-/uuid-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/uuid/-/uuid-2.0.1.tgz"
},
"write-file-atomic": {
"version": "1.1.3",
"from": "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-1.1.3.tgz",
"resolved": "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-1.1.3.tgz",
"dependencies": {
"slide": {
"version": "1.1.6",
"from": "https://registry.npmjs.org/slide/-/slide-1.1.6.tgz",
"resolved": "https://registry.npmjs.org/slide/-/slide-1.1.6.tgz"
}
}
},
"xdg-basedir": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/xdg-basedir/-/xdg-basedir-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/xdg-basedir/-/xdg-basedir-2.0.0.tgz",
"dependencies": {
"os-homedir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz"
}
}
}
}
},
"lodash.debounce": {
"version": "3.1.1",
"from": "https://registry.npmjs.org/lodash.debounce/-/lodash.debounce-3.1.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.debounce/-/lodash.debounce-3.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._getnative": {
"version": "3.9.1",
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
}
}
},
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"os-name": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/os-name/-/os-name-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/os-name/-/os-name-1.0.3.tgz",
"dependencies": {
"osx-release": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/osx-release/-/osx-release-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/osx-release/-/osx-release-1.1.0.tgz",
"dependencies": {
"minimist": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz"
}
}
},
"win-release": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/win-release/-/win-release-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/win-release/-/win-release-1.1.1.tgz",
"dependencies": {
"semver": {
"version": "5.0.3",
"from": "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz",
"resolved": "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"tough-cookie": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"is-root": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/is-root/-/is-root-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/is-root/-/is-root-1.0.0.tgz"
},
"junk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/junk/-/junk-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/junk/-/junk-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lockfile": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.1",
"from": "https://registry.npmjs.org/lockfile/-/lockfile-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/lockfile/-/lockfile-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lru-cache": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.7.0",
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz"
},
"md5-hex": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/md5-hex/-/md5-hex-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/md5-hex/-/md5-hex-1.1.0.tgz",
"dependencies": {
"md5-o-matic": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/md5-o-matic/-/md5-o-matic-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/md5-o-matic/-/md5-o-matic-0.1.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"mkdirp": {
"version": "0.5.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.0.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
},
"mout": {
"version": "0.11.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mout/-/mout-0.11.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mout/-/mout-0.11.0.tgz"
},
"nopt": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.4",
"from": "https://registry.npmjs.org/nopt/-/nopt-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"opn": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/opn/-/opn-1.0.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/opn/-/opn-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"p-throttler": {
"version": "0.1.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/p-throttler/-/p-throttler-0.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/p-throttler/-/p-throttler-0.1.1.tgz",
"dependencies": {
"q": {
"version": "0.9.7",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/q/-/q-0.9.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/q/-/q-0.9.7.tgz"
}
}
},
"promptly": {
"version": "0.2.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/promptly/-/promptly-0.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/promptly/-/promptly-0.2.0.tgz",
"dependencies": {
"read": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.7",
"from": "https://registry.npmjs.org/read/-/read-1.0.7.tgz",
"resolved": "https://registry.npmjs.org/read/-/read-1.0.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"mute-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.0.5",
"from": "https://registry.npmjs.org/mute-stream/-/mute-stream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/mute-stream/-/mute-stream-0.0.5.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"q": {
"version": "1.4.1",
"from": "https://registry.npmjs.org/q/-/q-1.4.1.tgz",
"resolved": "https://registry.npmjs.org/q/-/q-1.4.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"request": {
"version": "2.53.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/request/-/request-2.53.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/request/-/request-2.53.0.tgz",
"dependencies": {
"bl": {
"version": "0.9.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
},
"caseless": {
"version": "0.9.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/caseless/-/caseless-0.9.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.9.0.tgz"
},
"forever-agent": {
"version": "0.5.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.5.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.5.2.tgz"
},
"form-data": {
"version": "0.2.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/form-data/-/form-data-0.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/form-data/-/form-data-0.2.0.tgz",
"dependencies": {
"async": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.9.2",
"from": "https://registry.npmjs.org/async/-/async-0.9.2.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"json-stringify-safe": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.1",
"from": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"mime-types": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.14",
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"mime-db": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.12.0",
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"node-uuid": {
"version": "1.4.3",
"from": "https://registry.npmjs.org/node-uuid/-/node-uuid-1.4.3.tgz",
"resolved": "https://registry.npmjs.org/node-uuid/-/node-uuid-1.4.3.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"qs": {
"version": "2.3.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/qs/-/qs-2.3.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/qs/-/qs-2.3.3.tgz"
},
"tunnel-agent": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.1",
"from": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz",
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"tough-cookie": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.0",
"from": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"http-signature": {
"version": "0.10.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz",
"dependencies": {
"assert-plus": {
"version": "0.1.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
},
"asn1": {
"version": "0.1.11",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz"
},
"ctype": {
"version": "0.5.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz"
}
}
},
"oauth-sign": {
"version": "0.6.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.6.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.6.0.tgz"
},
"hawk": {
"version": "2.3.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/hawk/-/hawk-2.3.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/hawk/-/hawk-2.3.1.tgz",
"dependencies": {
"hoek": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.16.3",
"from": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz",
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"boom": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.9.0",
"from": "https://registry.npmjs.org/boom/-/boom-2.9.0.tgz",
"resolved": "https://registry.npmjs.org/boom/-/boom-2.9.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"cryptiles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.5",
"from": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz",
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"sntp": {
"version": "1.0.9",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz"
}
}
},
"aws-sign2": {
"version": "0.5.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.5.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.5.0.tgz"
},
"stringstream": {
"version": "0.0.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.4.tgz"
},
"combined-stream": {
"version": "0.0.7",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/combined-stream/-/combined-stream-0.0.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-0.0.7.tgz",
"dependencies": {
"delayed-stream": {
"version": "0.0.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-0.0.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-0.0.5.tgz"
}
}
},
"isstream": {
"version": "0.1.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
}
}
},
"request-progress": {
"version": "0.3.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/request-progress/-/request-progress-0.3.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/request-progress/-/request-progress-0.3.1.tgz",
"dependencies": {
"throttleit": {
"version": "0.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/throttleit/-/throttleit-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/throttleit/-/throttleit-0.0.2.tgz"
}
}
},
"retry": {
"version": "0.6.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/retry/-/retry-0.6.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/retry/-/retry-0.6.1.tgz"
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"minimatch": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.0.tgz",
"dependencies": {
"brace-expansion": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"dependencies": {
"balanced-match": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.0.tgz"
},
"concat-map": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
}
}
}
}
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"semver": {
"version": "2.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/semver/-/semver-2.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/semver/-/semver-2.3.2.tgz"
},
"shell-quote": {
"version": "1.4.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/shell-quote/-/shell-quote-1.4.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/shell-quote/-/shell-quote-1.4.3.tgz",
"dependencies": {
"jsonify": {
"version": "0.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/jsonify/-/jsonify-0.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/jsonify/-/jsonify-0.0.0.tgz"
},
"array-filter": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/array-filter/-/array-filter-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/array-filter/-/array-filter-0.0.1.tgz"
},
"array-reduce": {
"version": "0.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/array-reduce/-/array-reduce-0.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/array-reduce/-/array-reduce-0.0.0.tgz"
},
"array-map": {
"version": "0.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/array-map/-/array-map-0.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/array-map/-/array-map-0.0.0.tgz"
}
}
},
"stringify-object": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/stringify-object/-/stringify-object-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/stringify-object/-/stringify-object-1.0.1.tgz"
},
"tar-fs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.8.1",
"from": "https://registry.npmjs.org/tar-fs/-/tar-fs-1.8.1.tgz",
"resolved": "https://registry.npmjs.org/tar-fs/-/tar-fs-1.8.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"pump": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/pump/-/pump-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/pump/-/pump-1.0.0.tgz",
"dependencies": {
"end-of-stream": {
"version": "1.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz"
},
"once": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
},
"tar-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.1",
"from": "https://registry.npmjs.org/tar-stream/-/tar-stream-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-1.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"bl": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"end-of-stream": {
"version": "1.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz",
"dependencies": {
"once": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
},
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.2",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.2.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.0",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
"tmp": {
"version": "0.0.24",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/tmp/-/tmp-0.0.24.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/tmp/-/tmp-0.0.24.tgz"
},
"update-notifier": {
"version": "0.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/update-notifier/-/update-notifier-0.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/update-notifier/-/update-notifier-0.3.2.tgz",
"dependencies": {
"is-npm": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/is-npm/-/is-npm-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/is-npm/-/is-npm-1.0.0.tgz"
},
"latest-version": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.1",
"from": "https://registry.npmjs.org/latest-version/-/latest-version-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/latest-version/-/latest-version-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"package-json": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.0",
"from": "https://registry.npmjs.org/package-json/-/package-json-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/package-json/-/package-json-1.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"got": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.3.1",
"from": "https://registry.npmjs.org/got/-/got-3.3.1.tgz",
"resolved": "https://registry.npmjs.org/got/-/got-3.3.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"duplexify": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.4.2",
"from": "https://registry.npmjs.org/duplexify/-/duplexify-3.4.2.tgz",
"resolved": "https://registry.npmjs.org/duplexify/-/duplexify-3.4.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"end-of-stream": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.0.0.tgz",
"dependencies": {
"once": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
},
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.2",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.2.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
},
"infinity-agent": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "2.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/infinity-agent/-/infinity-agent-2.0.3.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/infinity-agent/-/infinity-agent-2.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-redirect": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-redirect/-/is-redirect-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-redirect/-/is-redirect-1.0.0.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"is-stream": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/is-stream/-/is-stream-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/is-stream/-/is-stream-1.0.1.tgz"
},
"lowercase-keys": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-1.0.0.tgz"
},
"nested-error-stacks": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.1",
"from": "https://registry.npmjs.org/nested-error-stacks/-/nested-error-stacks-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/nested-error-stacks/-/nested-error-stacks-1.0.1.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"object-assign": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"prepend-http": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.3",
"from": "https://registry.npmjs.org/prepend-http/-/prepend-http-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/prepend-http/-/prepend-http-1.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"read-all-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.1",
"from": "https://registry.npmjs.org/read-all-stream/-/read-all-stream-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-all-stream/-/read-all-stream-3.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.2",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.2.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
"timed-out": {
"version": "2.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/timed-out/-/timed-out-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/timed-out/-/timed-out-2.0.0.tgz"
}
}
},
"registry-url": {
"version": "3.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/registry-url/-/registry-url-3.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/registry-url/-/registry-url-3.0.3.tgz",
"dependencies": {
"rc": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.2",
"from": "https://registry.npmjs.org/rc/-/rc-1.1.2.tgz",
"resolved": "https://registry.npmjs.org/rc/-/rc-1.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"minimist": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.0",
"from": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"deep-extend": {
"version": "0.2.11",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/deep-extend/-/deep-extend-0.2.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/deep-extend/-/deep-extend-0.2.11.tgz"
},
"strip-json-comments": {
"version": "0.1.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-0.1.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-0.1.3.tgz"
},
"ini": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.3.4",
"from": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz",
"resolved": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
}
}
},
"semver-diff": {
"version": "2.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/semver-diff/-/semver-diff-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/semver-diff/-/semver-diff-2.0.0.tgz",
"dependencies": {
"semver": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.3.6",
"from": "https://registry.npmjs.org/semver/-/semver-4.3.6.tgz",
"resolved": "https://registry.npmjs.org/semver/-/semver-4.3.6.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"string-length": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.1",
"from": "https://registry.npmjs.org/string-length/-/string-length-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/string-length/-/string-length-1.0.1.tgz",
"dependencies": {
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"user-home": {
"version": "1.1.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/user-home/-/user-home-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/user-home/-/user-home-1.1.1.tgz"
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"which": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/which/-/which-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/which/-/which-1.2.0.tgz",
"dependencies": {
"is-absolute": {
"version": "0.1.7",
"from": "https://registry.npmjs.org/is-absolute/-/is-absolute-0.1.7.tgz",
"resolved": "https://registry.npmjs.org/is-absolute/-/is-absolute-0.1.7.tgz",
"dependencies": {
"is-relative": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/is-relative/-/is-relative-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/is-relative/-/is-relative-0.1.3.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"broccoli": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"version": "0.15.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/broccoli/-/broccoli-0.15.4.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/broccoli/-/broccoli-0.15.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"broccoli-kitchen-sink-helpers": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.2.9",
"from": "https://registry.npmjs.org/broccoli-kitchen-sink-helpers/-/broccoli-kitchen-sink-helpers-0.2.9.tgz",
"resolved": "https://registry.npmjs.org/broccoli-kitchen-sink-helpers/-/broccoli-kitchen-sink-helpers-0.2.9.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"mkdirp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.1",
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"glob": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
"commander": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.9.0",
"from": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"graceful-readlink": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz"
}
}
},
"connect": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.4.0",
"from": "https://registry.npmjs.org/connect/-/connect-3.4.0.tgz",
"resolved": "https://registry.npmjs.org/connect/-/connect-3.4.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"debug": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.0",
"from": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ms": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.7.1",
"from": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz",
"resolved": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"finalhandler": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.0",
"from": "https://registry.npmjs.org/finalhandler/-/finalhandler-0.4.0.tgz",
"resolved": "https://registry.npmjs.org/finalhandler/-/finalhandler-0.4.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"escape-html": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/escape-html/-/escape-html-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/escape-html/-/escape-html-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"on-finished": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.3.0",
"from": "https://registry.npmjs.org/on-finished/-/on-finished-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/on-finished/-/on-finished-2.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ee-first": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
"from": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"unpipe": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/unpipe/-/unpipe-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/unpipe/-/unpipe-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"parseurl": {
"version": "1.3.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/parseurl/-/parseurl-1.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/parseurl/-/parseurl-1.3.0.tgz"
},
"utils-merge": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/utils-merge/-/utils-merge-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/utils-merge/-/utils-merge-1.0.0.tgz"
}
}
},
"copy-dereference": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/copy-dereference/-/copy-dereference-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/copy-dereference/-/copy-dereference-1.0.0.tgz"
},
"findup-sync": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"version": "0.2.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.2.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"glob": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"version": "4.3.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"inflight": {
"version": "1.0.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"once": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
"handlebars": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"version": "3.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/handlebars/-/handlebars-3.0.3.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/handlebars/-/handlebars-3.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"optimist": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"version": "0.6.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"wordwrap": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "0.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
},
"minimist": {
"version": "0.0.10",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz"
}
}
},
"source-map": {
"version": "0.1.43",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/source-map/-/source-map-0.1.43.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.43.tgz",
"dependencies": {
"amdefine": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"uglify-js": {
"version": "2.3.6",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.3.6.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.3.6.tgz",
"dependencies": {
"async": {
"version": "0.2.10",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
},
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"optimist": {
"version": "0.3.7",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/optimist/-/optimist-0.3.7.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.3.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"wordwrap": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "0.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
"mime": {
"version": "1.3.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mime/-/mime-1.3.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mime/-/mime-1.3.4.tgz"
},
"promise-map-series": {
"version": "0.2.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/promise-map-series/-/promise-map-series-0.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/promise-map-series/-/promise-map-series-0.2.1.tgz"
},
"quick-temp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.3",
"from": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"rimraf": {
"version": "2.2.8",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz"
},
"mktemp": {
"version": "0.3.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz"
},
"underscore.string": {
"version": "2.3.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"
}
}
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"rsvp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.1.0",
"from": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"tiny-lr": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.7",
"from": "https://registry.npmjs.org/tiny-lr/-/tiny-lr-0.1.7.tgz",
"resolved": "https://registry.npmjs.org/tiny-lr/-/tiny-lr-0.1.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"body-parser": {
"version": "1.8.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/body-parser/-/body-parser-1.8.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/body-parser/-/body-parser-1.8.4.tgz",
"dependencies": {
"bytes": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/bytes/-/bytes-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/bytes/-/bytes-1.0.0.tgz"
},
"depd": {
"version": "0.4.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/depd/-/depd-0.4.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/depd/-/depd-0.4.5.tgz"
},
"iconv-lite": {
"version": "0.4.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.4.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.4.4.tgz"
},
"media-typer": {
"version": "0.3.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/media-typer/-/media-typer-0.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/media-typer/-/media-typer-0.3.0.tgz"
},
"on-finished": {
"version": "2.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/on-finished/-/on-finished-2.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/on-finished/-/on-finished-2.1.0.tgz",
"dependencies": {
"ee-first": {
"version": "1.0.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ee-first/-/ee-first-1.0.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.0.5.tgz"
}
}
},
"qs": {
"version": "2.2.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/qs/-/qs-2.2.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/qs/-/qs-2.2.4.tgz"
},
"raw-body": {
"version": "1.3.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/raw-body/-/raw-body-1.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/raw-body/-/raw-body-1.3.0.tgz"
},
"type-is": {
"version": "1.5.7",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/type-is/-/type-is-1.5.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/type-is/-/type-is-1.5.7.tgz",
"dependencies": {
"mime-types": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.14",
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"mime-db": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.12.0",
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
"debug": {
"version": "2.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-2.0.0.tgz",
"dependencies": {
"ms": {
"version": "0.6.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz"
}
}
},
"faye-websocket": {
"version": "0.7.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.7.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.7.3.tgz",
"dependencies": {
"websocket-driver": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.6.2",
"from": "https://registry.npmjs.org/websocket-driver/-/websocket-driver-0.6.2.tgz",
"resolved": "https://registry.npmjs.org/websocket-driver/-/websocket-driver-0.6.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"websocket-extensions": {
"version": "0.1.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/websocket-extensions/-/websocket-extensions-0.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/websocket-extensions/-/websocket-extensions-0.1.1.tgz"
}
}
}
}
},
"livereload-js": {
"version": "2.2.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/livereload-js/-/livereload-js-2.2.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/livereload-js/-/livereload-js-2.2.2.tgz"
},
"parseurl": {
"version": "1.3.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/parseurl/-/parseurl-1.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/parseurl/-/parseurl-1.3.0.tgz"
},
"qs": {
"version": "2.2.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/qs/-/qs-2.2.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/qs/-/qs-2.2.5.tgz"
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"broccoli-funnel": {
"version": "0.2.3",
"from": "git://github.com/igorminar/broccoli-funnel.git#6bfb53c4ca8dd3fa16416b9f85dc923a227e30ee",
"resolved": "git://github.com/igorminar/broccoli-funnel.git#6bfb53c4ca8dd3fa16416b9f85dc923a227e30ee",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"broccoli-read-compat": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/broccoli-read-compat/-/broccoli-read-compat-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/broccoli-read-compat/-/broccoli-read-compat-0.1.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"promise-map-series": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/promise-map-series/-/promise-map-series-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/promise-map-series/-/promise-map-series-0.2.1.tgz"
},
"quick-temp": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"rimraf": {
"version": "2.2.8",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"mktemp": {
"version": "0.3.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz"
},
"underscore.string": {
"version": "2.3.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"
}
}
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"rsvp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.1.0",
"from": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"core-object": {
"version": "0.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-object/-/core-object-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-object/-/core-object-0.0.2.tgz",
"dependencies": {
"lodash-node": {
"version": "2.4.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash-node/-/lodash-node-2.4.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash-node/-/lodash-node-2.4.1.tgz"
}
}
},
"mkdirp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.1",
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"minimist": {
"version": "0.0.8",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"walk-sync": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/walk-sync/-/walk-sync-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/walk-sync/-/walk-sync-0.1.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"broccoli-slow-trees": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/broccoli-slow-trees/-/broccoli-slow-trees-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/broccoli-slow-trees/-/broccoli-slow-trees-1.1.0.tgz"
},
"broccoli-stew": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/broccoli-stew/-/broccoli-stew-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/broccoli-stew/-/broccoli-stew-0.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"broccoli-filter": {
"version": "0.1.14",
"from": "https://registry.npmjs.org/broccoli-filter/-/broccoli-filter-0.1.14.tgz",
"resolved": "https://registry.npmjs.org/broccoli-filter/-/broccoli-filter-0.1.14.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"broccoli-kitchen-sink-helpers": {
"version": "0.2.9",
"from": "https://registry.npmjs.org/broccoli-kitchen-sink-helpers/-/broccoli-kitchen-sink-helpers-0.2.9.tgz",
"resolved": "https://registry.npmjs.org/broccoli-kitchen-sink-helpers/-/broccoli-kitchen-sink-helpers-0.2.9.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"mkdirp": {
"version": "0.5.1",
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
},
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"mkdirp": {
"version": "0.3.5",
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz"
},
"promise-map-series": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/promise-map-series/-/promise-map-series-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/promise-map-series/-/promise-map-series-0.2.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"quick-temp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.3",
"from": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"rimraf": {
"version": "2.2.8",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz"
},
"mktemp": {
"version": "0.3.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz"
},
"underscore.string": {
"version": "2.3.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"
}
}
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"broccoli-funnel": {
"version": "0.1.7",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/broccoli-funnel/-/broccoli-funnel-0.1.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/broccoli-funnel/-/broccoli-funnel-0.1.7.tgz",
"dependencies": {
"core-object": {
"version": "0.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-object/-/core-object-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-object/-/core-object-0.0.2.tgz"
},
"mkdirp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.1",
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"minimist": {
"version": "0.0.8",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
}
}
},
"broccoli-merge-trees": {
"version": "0.2.4",
"from": "https://registry.npmjs.org/broccoli-merge-trees/-/broccoli-merge-trees-0.2.4.tgz",
"resolved": "https://registry.npmjs.org/broccoli-merge-trees/-/broccoli-merge-trees-0.2.4.tgz",
"dependencies": {
"broccoli-plugin": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/broccoli-plugin/-/broccoli-plugin-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/broccoli-plugin/-/broccoli-plugin-1.2.1.tgz",
"dependencies": {
"promise-map-series": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/promise-map-series/-/promise-map-series-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/promise-map-series/-/promise-map-series-0.2.1.tgz"
},
"quick-temp": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
"dependencies": {
"rimraf": {
"version": "2.2.8",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz"
},
"mktemp": {
"version": "0.3.5",
"from": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz",
"resolved": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz"
},
"underscore.string": {
"version": "2.3.3",
"from": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz",
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"
}
}
},
"rimraf": {
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"chalk": {
"version": "0.5.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/chalk/-/chalk-0.5.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/chalk/-/chalk-0.5.1.tgz",
"dependencies": {
"ansi-styles": {
"version": "1.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-1.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-1.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "0.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-0.1.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "0.2.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz"
}
}
},
"strip-ansi": {
"version": "0.3.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-0.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-0.3.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "0.2.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz"
}
}
},
"supports-color": {
"version": "0.2.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/supports-color/-/supports-color-0.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-0.2.0.tgz"
}
}
},
"debug": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.0",
"from": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ms": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.7.1",
"from": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz",
"resolved": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"fs-extra": {
"version": "0.13.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/fs-extra/-/fs-extra-0.13.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-0.13.0.tgz",
"dependencies": {
"ncp": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ncp/-/ncp-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ncp/-/ncp-1.0.1.tgz"
},
"jsonfile": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.3",
"from": "https://registry.npmjs.org/jsonfile/-/jsonfile-2.2.3.tgz",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-2.2.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"lodash-node": {
"version": "2.4.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash-node/-/lodash-node-2.4.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash-node/-/lodash-node-2.4.1.tgz"
},
"rsvp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.1.0",
"from": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz"
},
"walk-sync": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/walk-sync/-/walk-sync-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/walk-sync/-/walk-sync-0.1.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"broccoli-writer": {
"version": "0.1.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/broccoli-writer/-/broccoli-writer-0.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/broccoli-writer/-/broccoli-writer-0.1.1.tgz",
"dependencies": {
"quick-temp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.3",
"from": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"rimraf": {
"version": "2.2.8",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz"
},
"mktemp": {
"version": "0.3.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mktemp/-/mktemp-0.3.5.tgz"
},
"underscore.string": {
"version": "2.3.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"
}
}
},
"rsvp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.1.0",
"from": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"browserify": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "10.2.6",
"from": "https://registry.npmjs.org/browserify/-/browserify-10.2.6.tgz",
"resolved": "https://registry.npmjs.org/browserify/-/browserify-10.2.6.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"JSONStream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.6",
"from": "https://registry.npmjs.org/JSONStream/-/JSONStream-1.0.6.tgz",
"resolved": "https://registry.npmjs.org/JSONStream/-/JSONStream-1.0.6.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"jsonparse": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.0",
"from": "https://registry.npmjs.org/jsonparse/-/jsonparse-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/jsonparse/-/jsonparse-1.2.0.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"through": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.3.8",
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
}
}
},
"assert": {
"version": "1.3.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/assert/-/assert-1.3.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/assert/-/assert-1.3.0.tgz"
},
"browser-pack": {
"version": "5.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/browser-pack/-/browser-pack-5.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/browser-pack/-/browser-pack-5.0.1.tgz",
"dependencies": {
"combine-source-map": {
"version": "0.6.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/combine-source-map/-/combine-source-map-0.6.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/combine-source-map/-/combine-source-map-0.6.1.tgz",
"dependencies": {
"convert-source-map": {
"version": "1.1.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.1.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.1.1.tgz"
},
"inline-source-map": {
"version": "0.5.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/inline-source-map/-/inline-source-map-0.5.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/inline-source-map/-/inline-source-map-0.5.0.tgz"
},
"lodash.memoize": {
"version": "3.0.4",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/lodash.memoize/-/lodash.memoize-3.0.4.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/lodash.memoize/-/lodash.memoize-3.0.4.tgz"
},
"source-map": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.4",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"amdefine": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
}
}
}
}
},
"umd": {
"version": "3.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/umd/-/umd-3.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/umd/-/umd-3.0.1.tgz"
}
}
},
"browser-resolve": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.10.1",
"from": "https://registry.npmjs.org/browser-resolve/-/browser-resolve-1.10.1.tgz",
"resolved": "https://registry.npmjs.org/browser-resolve/-/browser-resolve-1.10.1.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"browserify-zlib": {
"version": "0.1.4",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/browserify-zlib/-/browserify-zlib-0.1.4.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/browserify-zlib/-/browserify-zlib-0.1.4.tgz",
"dependencies": {
"pako": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.2.8",
"from": "https://registry.npmjs.org/pako/-/pako-0.2.8.tgz",
"resolved": "https://registry.npmjs.org/pako/-/pako-0.2.8.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
}
}
},
"buffer": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.5.1",
"from": "https://registry.npmjs.org/buffer/-/buffer-3.5.1.tgz",
"resolved": "https://registry.npmjs.org/buffer/-/buffer-3.5.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"ieee754": {
"version": "1.1.6",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/ieee754/-/ieee754-1.1.6.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/ieee754/-/ieee754-1.1.6.tgz"
},
"is-array": {
"version": "1.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/is-array/-/is-array-1.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/is-array/-/is-array-1.0.1.tgz"
}
}
},
"builtins": {
"version": "0.0.7",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/builtins/-/builtins-0.0.7.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/builtins/-/builtins-0.0.7.tgz"
},
"commondir": {
"version": "0.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/commondir/-/commondir-0.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/commondir/-/commondir-0.0.1.tgz"
},
"concat-stream": {
"version": "1.4.10",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.4.10.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.4.10.tgz",
"dependencies": {
"typedarray": {
"version": "0.0.6",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz"
}
}
},
"console-browserify": {
"version": "1.1.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/console-browserify/-/console-browserify-1.1.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/console-browserify/-/console-browserify-1.1.0.tgz",
"dependencies": {
"date-now": {
"version": "0.1.4",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/date-now/-/date-now-0.1.4.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/date-now/-/date-now-0.1.4.tgz"
}
}
},
"constants-browserify": {
"version": "0.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/constants-browserify/-/constants-browserify-0.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/constants-browserify/-/constants-browserify-0.0.1.tgz"
},
"crypto-browserify": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.11.0",
"from": "https://registry.npmjs.org/crypto-browserify/-/crypto-browserify-3.11.0.tgz",
"resolved": "https://registry.npmjs.org/crypto-browserify/-/crypto-browserify-3.11.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"browserify-cipher": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/browserify-cipher/-/browserify-cipher-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/browserify-cipher/-/browserify-cipher-1.0.0.tgz",
"dependencies": {
"browserify-aes": {
"version": "1.0.5",
"from": "https://registry.npmjs.org/browserify-aes/-/browserify-aes-1.0.5.tgz",
"resolved": "https://registry.npmjs.org/browserify-aes/-/browserify-aes-1.0.5.tgz",
"dependencies": {
"buffer-xor": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/buffer-xor/-/buffer-xor-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/buffer-xor/-/buffer-xor-1.0.3.tgz"
},
"cipher-base": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz"
}
}
},
"browserify-des": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/browserify-des/-/browserify-des-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/browserify-des/-/browserify-des-1.0.0.tgz",
"dependencies": {
"cipher-base": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz"
},
"des.js": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/des.js/-/des.js-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/des.js/-/des.js-1.0.0.tgz",
"dependencies": {
"minimalistic-assert": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.0.tgz"
}
}
}
}
},
"evp_bytestokey": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/evp_bytestokey/-/evp_bytestokey-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/evp_bytestokey/-/evp_bytestokey-1.0.0.tgz"
}
}
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"browserify-sign": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/browserify-sign/-/browserify-sign-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/browserify-sign/-/browserify-sign-4.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"bn.js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.1.1",
"from": "https://registry.npmjs.org/bn.js/-/bn.js-4.1.1.tgz",
"resolved": "https://registry.npmjs.org/bn.js/-/bn.js-4.1.1.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"browserify-rsa": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/browserify-rsa/-/browserify-rsa-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/browserify-rsa/-/browserify-rsa-4.0.0.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"elliptic": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "6.0.1",
"from": "https://registry.npmjs.org/elliptic/-/elliptic-6.0.1.tgz",
"resolved": "https://registry.npmjs.org/elliptic/-/elliptic-6.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"brorand": {
"version": "1.0.5",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/brorand/-/brorand-1.0.5.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/brorand/-/brorand-1.0.5.tgz"
},
"hash.js": {
"version": "1.0.3",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/hash.js/-/hash.js-1.0.3.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/hash.js/-/hash.js-1.0.3.tgz"
}
}
},
"parse-asn1": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.0",
"from": "https://registry.npmjs.org/parse-asn1/-/parse-asn1-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/parse-asn1/-/parse-asn1-5.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"asn1.js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/asn1.js/-/asn1.js-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/asn1.js/-/asn1.js-4.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"minimalistic-assert": {
"version": "1.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.0.tgz"
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"browserify-aes": {
"version": "1.0.5",
"from": "https://registry.npmjs.org/browserify-aes/-/browserify-aes-1.0.5.tgz",
"resolved": "https://registry.npmjs.org/browserify-aes/-/browserify-aes-1.0.5.tgz",
"dependencies": {
"buffer-xor": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/buffer-xor/-/buffer-xor-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/buffer-xor/-/buffer-xor-1.0.3.tgz"
},
"cipher-base": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz"
}
}
},
"evp_bytestokey": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/evp_bytestokey/-/evp_bytestokey-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/evp_bytestokey/-/evp_bytestokey-1.0.0.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
}
}
}
}
},
"create-ecdh": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/create-ecdh/-/create-ecdh-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/create-ecdh/-/create-ecdh-4.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"bn.js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.1.1",
"from": "https://registry.npmjs.org/bn.js/-/bn.js-4.1.1.tgz",
"resolved": "https://registry.npmjs.org/bn.js/-/bn.js-4.1.1.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"elliptic": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "6.0.1",
"from": "https://registry.npmjs.org/elliptic/-/elliptic-6.0.1.tgz",
"resolved": "https://registry.npmjs.org/elliptic/-/elliptic-6.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"brorand": {
"version": "1.0.5",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/brorand/-/brorand-1.0.5.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/brorand/-/brorand-1.0.5.tgz"
},
"hash.js": {
"version": "1.0.3",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/hash.js/-/hash.js-1.0.3.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/hash.js/-/hash.js-1.0.3.tgz"
}
}
}
}
},
"create-hash": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.2",
"from": "https://registry.npmjs.org/create-hash/-/create-hash-1.1.2.tgz",
"resolved": "https://registry.npmjs.org/create-hash/-/create-hash-1.1.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"cipher-base": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz"
},
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"ripemd160": {
"version": "1.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/ripemd160/-/ripemd160-1.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/ripemd160/-/ripemd160-1.0.1.tgz"
},
"sha.js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.4",
"from": "https://registry.npmjs.org/sha.js/-/sha.js-2.4.4.tgz",
"resolved": "https://registry.npmjs.org/sha.js/-/sha.js-2.4.4.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
}
}
},
"create-hmac": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.4",
"from": "https://registry.npmjs.org/create-hmac/-/create-hmac-1.1.4.tgz",
"resolved": "https://registry.npmjs.org/create-hmac/-/create-hmac-1.1.4.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"diffie-hellman": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.0",
"from": "https://registry.npmjs.org/diffie-hellman/-/diffie-hellman-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/diffie-hellman/-/diffie-hellman-5.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"bn.js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.1.1",
"from": "https://registry.npmjs.org/bn.js/-/bn.js-4.1.1.tgz",
"resolved": "https://registry.npmjs.org/bn.js/-/bn.js-4.1.1.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"miller-rabin": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/miller-rabin/-/miller-rabin-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/miller-rabin/-/miller-rabin-4.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"brorand": {
"version": "1.0.5",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/brorand/-/brorand-1.0.5.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/brorand/-/brorand-1.0.5.tgz"
}
}
}
}
},
"pbkdf2": {
"version": "3.0.4",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/pbkdf2/-/pbkdf2-3.0.4.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/pbkdf2/-/pbkdf2-3.0.4.tgz"
},
"public-encrypt": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/public-encrypt/-/public-encrypt-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/public-encrypt/-/public-encrypt-4.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"bn.js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.1.1",
"from": "https://registry.npmjs.org/bn.js/-/bn.js-4.1.1.tgz",
"resolved": "https://registry.npmjs.org/bn.js/-/bn.js-4.1.1.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"browserify-rsa": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/browserify-rsa/-/browserify-rsa-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/browserify-rsa/-/browserify-rsa-4.0.0.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"parse-asn1": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.0",
"from": "https://registry.npmjs.org/parse-asn1/-/parse-asn1-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/parse-asn1/-/parse-asn1-5.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"asn1.js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/asn1.js/-/asn1.js-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/asn1.js/-/asn1.js-4.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"minimalistic-assert": {
"version": "1.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.0.tgz"
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"browserify-aes": {
"version": "1.0.5",
"from": "https://registry.npmjs.org/browserify-aes/-/browserify-aes-1.0.5.tgz",
"resolved": "https://registry.npmjs.org/browserify-aes/-/browserify-aes-1.0.5.tgz",
"dependencies": {
"buffer-xor": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/buffer-xor/-/buffer-xor-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/buffer-xor/-/buffer-xor-1.0.3.tgz"
},
"cipher-base": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/cipher-base/-/cipher-base-1.0.2.tgz"
}
}
},
"evp_bytestokey": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/evp_bytestokey/-/evp_bytestokey-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/evp_bytestokey/-/evp_bytestokey-1.0.0.tgz"
}
}
}
}
},
"randombytes": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/randombytes/-/randombytes-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/randombytes/-/randombytes-2.0.1.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
}
}
},
"defined": {
"version": "1.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/defined/-/defined-1.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/defined/-/defined-1.0.0.tgz"
},
"deps-sort": {
"version": "1.3.9",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/deps-sort/-/deps-sort-1.3.9.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/deps-sort/-/deps-sort-1.3.9.tgz"
},
"domain-browser": {
"version": "1.1.4",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/domain-browser/-/domain-browser-1.1.4.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/domain-browser/-/domain-browser-1.1.4.tgz"
},
"duplexer2": {
"version": "0.0.2",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz"
},
"events": {
"version": "1.0.2",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/events/-/events-1.0.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/events/-/events-1.0.2.tgz"
},
"has": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.1",
"from": "https://registry.npmjs.org/has/-/has-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/has/-/has-1.0.1.tgz",
"dependencies": {
"function-bind": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/function-bind/-/function-bind-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.0.2.tgz"
}
}
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"htmlescape": {
"version": "1.1.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/htmlescape/-/htmlescape-1.1.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/htmlescape/-/htmlescape-1.1.0.tgz"
},
"http-browserify": {
"version": "1.7.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/http-browserify/-/http-browserify-1.7.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/http-browserify/-/http-browserify-1.7.0.tgz",
"dependencies": {
"Base64": {
"version": "0.2.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/Base64/-/Base64-0.2.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/Base64/-/Base64-0.2.1.tgz"
}
}
},
"https-browserify": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.0.1",
"from": "https://registry.npmjs.org/https-browserify/-/https-browserify-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/https-browserify/-/https-browserify-0.0.1.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"inherits": {
"version": "2.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"insert-module-globals": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "6.6.3",
"from": "https://registry.npmjs.org/insert-module-globals/-/insert-module-globals-6.6.3.tgz",
"resolved": "https://registry.npmjs.org/insert-module-globals/-/insert-module-globals-6.6.3.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"combine-source-map": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.6.1",
"from": "https://registry.npmjs.org/combine-source-map/-/combine-source-map-0.6.1.tgz",
"resolved": "https://registry.npmjs.org/combine-source-map/-/combine-source-map-0.6.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"convert-source-map": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.1.1.tgz"
},
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"inline-source-map": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.0",
"from": "https://registry.npmjs.org/inline-source-map/-/inline-source-map-0.5.0.tgz",
"resolved": "https://registry.npmjs.org/inline-source-map/-/inline-source-map-0.5.0.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.memoize": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.memoize/-/lodash.memoize-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.memoize/-/lodash.memoize-3.0.4.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"source-map": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.4",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"amdefine": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-buffer": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.0.tgz"
},
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"lexical-scope": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.0",
"from": "https://registry.npmjs.org/lexical-scope/-/lexical-scope-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/lexical-scope/-/lexical-scope-1.2.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"astw": {
"version": "2.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/astw/-/astw-2.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/astw/-/astw-2.0.0.tgz",
"dependencies": {
"acorn": {
"version": "1.2.2",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/acorn/-/acorn-1.2.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/acorn/-/acorn-1.2.2.tgz"
}
}
}
}
}
}
},
"isarray": {
"version": "0.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"labeled-stream-splicer": {
"version": "1.0.2",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/labeled-stream-splicer/-/labeled-stream-splicer-1.0.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/labeled-stream-splicer/-/labeled-stream-splicer-1.0.2.tgz",
"dependencies": {
"stream-splicer": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.3.2",
"from": "https://registry.npmjs.org/stream-splicer/-/stream-splicer-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/stream-splicer/-/stream-splicer-1.3.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"readable-wrap": {
"version": "1.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/readable-wrap/-/readable-wrap-1.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/readable-wrap/-/readable-wrap-1.0.0.tgz"
},
"indexof": {
"version": "0.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz"
}
}
}
}
},
"module-deps": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.9.1",
"from": "https://registry.npmjs.org/module-deps/-/module-deps-3.9.1.tgz",
"resolved": "https://registry.npmjs.org/module-deps/-/module-deps-3.9.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"detective": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.3.1",
"from": "https://registry.npmjs.org/detective/-/detective-4.3.1.tgz",
"resolved": "https://registry.npmjs.org/detective/-/detective-4.3.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"acorn": {
"version": "1.2.2",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/acorn/-/acorn-1.2.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/acorn/-/acorn-1.2.2.tgz"
}
}
},
"stream-combiner2": {
"version": "1.0.2",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/stream-combiner2/-/stream-combiner2-1.0.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/stream-combiner2/-/stream-combiner2-1.0.2.tgz",
"dependencies": {
"through2": {
"version": "0.5.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/through2/-/through2-0.5.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/through2/-/through2-0.5.1.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
}
}
},
"xtend": {
"version": "3.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/xtend/-/xtend-3.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/xtend/-/xtend-3.0.0.tgz"
}
}
}
}
}
}
},
"os-browserify": {
"version": "0.1.2",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/os-browserify/-/os-browserify-0.1.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/os-browserify/-/os-browserify-0.1.2.tgz"
},
"parents": {
"version": "1.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/parents/-/parents-1.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/parents/-/parents-1.0.1.tgz",
"dependencies": {
"path-platform": {
"version": "0.11.15",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/path-platform/-/path-platform-0.11.15.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/path-platform/-/path-platform-0.11.15.tgz"
}
}
},
"path-browserify": {
"version": "0.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/path-browserify/-/path-browserify-0.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/path-browserify/-/path-browserify-0.0.0.tgz"
},
"process": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.11.2",
"from": "https://registry.npmjs.org/process/-/process-0.11.2.tgz",
"resolved": "https://registry.npmjs.org/process/-/process-0.11.2.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
},
"punycode": {
"version": "1.3.2",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/punycode/-/punycode-1.3.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/punycode/-/punycode-1.3.2.tgz"
},
"querystring-es3": {
"version": "0.2.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/querystring-es3/-/querystring-es3-0.2.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/querystring-es3/-/querystring-es3-0.2.1.tgz"
},
"read-only-stream": {
"version": "1.1.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/read-only-stream/-/read-only-stream-1.1.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/read-only-stream/-/read-only-stream-1.1.1.tgz",
"dependencies": {
"readable-wrap": {
"version": "1.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/readable-wrap/-/readable-wrap-1.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/readable-wrap/-/readable-wrap-1.0.0.tgz"
}
}
},
"readable-stream": {
"version": "1.1.13",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
}
}
},
"resolve": {
"version": "1.1.6",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/resolve/-/resolve-1.1.6.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.1.6.tgz"
},
"shasum": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/shasum/-/shasum-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/shasum/-/shasum-1.0.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"dependencies": {
"json-stable-stringify": {
"version": "0.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/json-stable-stringify/-/json-stable-stringify-0.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/json-stable-stringify/-/json-stable-stringify-0.0.1.tgz",
"dependencies": {
"jsonify": {
"version": "0.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/jsonify/-/jsonify-0.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/jsonify/-/jsonify-0.0.0.tgz"
}
}
},
"sha.js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.4",
"from": "https://registry.npmjs.org/sha.js/-/sha.js-2.4.4.tgz",
"resolved": "https://registry.npmjs.org/sha.js/-/sha.js-2.4.4.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
}
}
},
"shell-quote": {
"version": "0.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/shell-quote/-/shell-quote-0.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/shell-quote/-/shell-quote-0.0.1.tgz"
},
"stream-browserify": {
"version": "1.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/stream-browserify/-/stream-browserify-1.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/stream-browserify/-/stream-browserify-1.0.0.tgz"
},
"string_decoder": {
"version": "0.10.31",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"subarg": {
"version": "1.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/subarg/-/subarg-1.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/subarg/-/subarg-1.0.0.tgz"
},
"syntax-error": {
"version": "1.1.4",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/syntax-error/-/syntax-error-1.1.4.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/syntax-error/-/syntax-error-1.1.4.tgz",
"dependencies": {
"acorn": {
"version": "1.2.2",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/acorn/-/acorn-1.2.2.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/acorn/-/acorn-1.2.2.tgz"
}
}
},
"through2": {
"version": "1.1.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/through2/-/through2-1.1.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/through2/-/through2-1.1.1.tgz"
},
"timers-browserify": {
"version": "1.4.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/timers-browserify/-/timers-browserify-1.4.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/timers-browserify/-/timers-browserify-1.4.1.tgz"
},
"tty-browserify": {
"version": "0.0.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/tty-browserify/-/tty-browserify-0.0.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/tty-browserify/-/tty-browserify-0.0.0.tgz"
},
"url": {
"version": "0.10.3",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/url/-/url-0.10.3.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/url/-/url-0.10.3.tgz",
"dependencies": {
"querystring": {
"version": "0.2.0",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/querystring/-/querystring-0.2.0.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/querystring/-/querystring-0.2.0.tgz"
}
}
},
"util": {
"version": "0.10.3",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/util/-/util-0.10.3.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/util/-/util-0.10.3.tgz"
},
"vm-browserify": {
"version": "0.0.4",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/vm-browserify/-/vm-browserify-0.0.4.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/vm-browserify/-/vm-browserify-0.0.4.tgz",
"dependencies": {
"indexof": {
"version": "0.0.1",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"from": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz",
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
"resolved": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz"
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(benchpress): add browserify bundling Use browserify to bundle benchpress and its dependencies.
2015-06-23 18:26:51 -04:00
}
}
},
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"browserstacktunnel-wrapper": {
"version": "1.4.2",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/browserstacktunnel-wrapper/-/browserstacktunnel-wrapper-1.4.2.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/browserstacktunnel-wrapper/-/browserstacktunnel-wrapper-1.4.2.tgz",
"dependencies": {
"unzip": {
"version": "0.1.11",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/unzip/-/unzip-0.1.11.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/unzip/-/unzip-0.1.11.tgz",
"dependencies": {
"fstream": {
"version": "0.1.31",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/fstream/-/fstream-0.1.31.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/fstream/-/fstream-0.1.31.tgz",
"dependencies": {
"graceful-fs": {
"version": "3.0.8",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"mkdirp": {
"version": "0.5.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
},
"rimraf": {
"version": "2.4.3",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"once": {
"version": "1.3.2",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
}
}
},
"pullstream": {
"version": "0.4.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/pullstream/-/pullstream-0.4.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/pullstream/-/pullstream-0.4.1.tgz",
"dependencies": {
"over": {
"version": "0.0.5",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/over/-/over-0.0.5.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/over/-/over-0.0.5.tgz"
},
"slice-stream": {
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/slice-stream/-/slice-stream-1.0.0.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/slice-stream/-/slice-stream-1.0.0.tgz"
}
}
},
"binary": {
"version": "0.3.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/binary/-/binary-0.3.0.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/binary/-/binary-0.3.0.tgz",
"dependencies": {
"chainsaw": {
"version": "0.1.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/chainsaw/-/chainsaw-0.1.0.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/chainsaw/-/chainsaw-0.1.0.tgz",
"dependencies": {
"traverse": {
"version": "0.3.9",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/traverse/-/traverse-0.3.9.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/traverse/-/traverse-0.3.9.tgz"
}
}
},
"buffers": {
"version": "0.1.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/buffers/-/buffers-0.1.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/buffers/-/buffers-0.1.1.tgz"
}
}
},
"readable-stream": {
"version": "1.0.33",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"setimmediate": {
"version": "1.0.4",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/setimmediate/-/setimmediate-1.0.4.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/setimmediate/-/setimmediate-1.0.4.tgz"
},
"match-stream": {
"version": "0.0.2",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/match-stream/-/match-stream-0.0.2.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/match-stream/-/match-stream-0.0.2.tgz",
"dependencies": {
"buffers": {
"version": "0.1.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/buffers/-/buffers-0.1.1.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/buffers/-/buffers-0.1.1.tgz"
}
}
}
}
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"canonical-path": {
"version": "0.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/canonical-path/-/canonical-path-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/canonical-path/-/canonical-path-0.0.2.tgz"
},
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"chokidar": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.0",
"from": "https://registry.npmjs.org/chokidar/-/chokidar-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/chokidar/-/chokidar-1.2.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
"anymatch": {
"version": "1.3.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/anymatch/-/anymatch-1.3.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/anymatch/-/anymatch-1.3.0.tgz",
"dependencies": {
"micromatch": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.2.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/micromatch/-/micromatch-2.2.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-2.2.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
"arr-diff": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/arr-diff/-/arr-diff-1.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/arr-diff/-/arr-diff-1.1.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"arr-flatten": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/arr-flatten/-/arr-flatten-1.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/arr-flatten/-/arr-flatten-1.0.1.tgz"
},
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"array-slice": {
"version": "0.2.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/array-slice/-/array-slice-0.2.3.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/array-slice/-/array-slice-0.2.3.tgz"
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"array-unique": {
"version": "0.2.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/array-unique/-/array-unique-0.2.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/array-unique/-/array-unique-0.2.1.tgz"
},
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"braces": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.8.2",
"from": "https://registry.npmjs.org/braces/-/braces-1.8.2.tgz",
"resolved": "https://registry.npmjs.org/braces/-/braces-1.8.2.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
"expand-range": {
"version": "1.8.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/expand-range/-/expand-range-1.8.1.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/expand-range/-/expand-range-1.8.1.tgz",
"dependencies": {
"fill-range": {
"version": "2.2.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/fill-range/-/fill-range-2.2.2.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-2.2.2.tgz",
"dependencies": {
"is-number": {
"version": "1.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/is-number/-/is-number-1.1.2.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/is-number/-/is-number-1.1.2.tgz"
},
"isobject": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isobject/-/isobject-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/isobject/-/isobject-1.0.2.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
},
"randomatic": {
"version": "1.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/randomatic/-/randomatic-1.1.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/randomatic/-/randomatic-1.1.0.tgz"
},
"repeat-string": {
"version": "1.5.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.5.2.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.5.2.tgz"
}
}
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"lazy-cache": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.2.4",
"from": "https://registry.npmjs.org/lazy-cache/-/lazy-cache-0.2.4.tgz",
"resolved": "https://registry.npmjs.org/lazy-cache/-/lazy-cache-0.2.4.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"preserve": {
"version": "0.2.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/preserve/-/preserve-0.2.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/preserve/-/preserve-0.2.0.tgz"
},
"repeat-element": {
"version": "1.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/repeat-element/-/repeat-element-1.1.2.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/repeat-element/-/repeat-element-1.1.2.tgz"
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"expand-brackets": {
"version": "0.1.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/expand-brackets/-/expand-brackets-0.1.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/expand-brackets/-/expand-brackets-0.1.4.tgz"
},
"extglob": {
"version": "0.3.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/extglob/-/extglob-0.3.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/extglob/-/extglob-0.3.1.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"ansi-green": {
"version": "0.1.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ansi-green/-/ansi-green-0.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ansi-green/-/ansi-green-0.1.1.tgz",
"dependencies": {
"ansi-wrap": {
"version": "0.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ansi-wrap/-/ansi-wrap-0.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ansi-wrap/-/ansi-wrap-0.1.0.tgz"
}
}
},
"is-extglob": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/is-extglob/-/is-extglob-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-1.0.0.tgz"
},
"success-symbol": {
"version": "0.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/success-symbol/-/success-symbol-0.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/success-symbol/-/success-symbol-0.1.0.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
}
}
},
"filename-regex": {
"version": "2.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/filename-regex/-/filename-regex-2.0.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/filename-regex/-/filename-regex-2.0.0.tgz"
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"is-glob": {
"version": "1.1.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/is-glob/-/is-glob-1.1.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-1.1.3.tgz"
},
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"kind-of": {
"version": "1.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/kind-of/-/kind-of-1.1.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-1.1.0.tgz"
},
"object.omit": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/object.omit/-/object.omit-1.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/object.omit/-/object.omit-1.1.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
"for-own": {
"version": "0.1.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/for-own/-/for-own-0.1.3.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/for-own/-/for-own-0.1.3.tgz",
"dependencies": {
"for-in": {
"version": "0.1.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/for-in/-/for-in-0.1.4.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/for-in/-/for-in-0.1.4.tgz"
}
}
},
"isobject": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isobject/-/isobject-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/isobject/-/isobject-1.0.2.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
}
}
},
"parse-glob": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "3.0.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/parse-glob/-/parse-glob-3.0.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/parse-glob/-/parse-glob-3.0.4.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
"glob-base": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "0.3.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/glob-base/-/glob-base-0.3.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/glob-base/-/glob-base-0.3.0.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
},
"is-dotfile": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/is-dotfile/-/is-dotfile-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/is-dotfile/-/is-dotfile-1.0.2.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
},
"is-extglob": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/is-extglob/-/is-extglob-1.0.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-1.0.0.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"is-glob": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.1",
"from": "https://registry.npmjs.org/is-glob/-/is-glob-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-2.0.1.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
}
}
},
"regex-cache": {
"version": "0.4.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/regex-cache/-/regex-cache-0.4.2.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/regex-cache/-/regex-cache-0.4.2.tgz",
"dependencies": {
"is-equal-shallow": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "0.1.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/is-equal-shallow/-/is-equal-shallow-0.1.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/is-equal-shallow/-/is-equal-shallow-0.1.3.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
},
"is-primitive": {
"version": "2.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/is-primitive/-/is-primitive-2.0.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/is-primitive/-/is-primitive-2.0.0.tgz"
}
}
}
}
}
}
},
"arrify": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/arrify/-/arrify-1.0.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/arrify/-/arrify-1.0.0.tgz"
},
"async-each": {
"version": "0.1.6",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/async-each/-/async-each-0.1.6.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/async-each/-/async-each-0.1.6.tgz"
},
"glob-parent": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
},
"is-binary-path": {
fix(shrinkwrap): restore fsevents dependency Fixes #2511
2015-06-12 13:21:42 -04:00
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/is-binary-path/-/is-binary-path-1.0.1.tgz",
fix(shrinkwrap): restore fsevents dependency Fixes #2511
2015-06-12 13:21:42 -04:00
"resolved": "https://registry.npmjs.org/is-binary-path/-/is-binary-path-1.0.1.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
"binary-extensions": {
fix(shrinkwrap): restore fsevents dependency Fixes #2511
2015-06-12 13:21:42 -04:00
"version": "1.3.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/binary-extensions/-/binary-extensions-1.3.1.tgz",
fix(shrinkwrap): restore fsevents dependency Fixes #2511
2015-06-12 13:21:42 -04:00
"resolved": "https://registry.npmjs.org/binary-extensions/-/binary-extensions-1.3.1.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
}
}
},
"is-glob": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.1",
"from": "https://registry.npmjs.org/is-glob/-/is-glob-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-2.0.1.tgz",
"dependencies": {
"is-extglob": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-extglob/-/is-extglob-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-1.0.0.tgz"
}
}
},
"lodash.flatten": {
"version": "3.0.2",
"from": "https://registry.npmjs.org/lodash.flatten/-/lodash.flatten-3.0.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.flatten/-/lodash.flatten-3.0.2.tgz",
"dependencies": {
"lodash._baseflatten": {
"version": "3.1.4",
"from": "https://registry.npmjs.org/lodash._baseflatten/-/lodash._baseflatten-3.1.4.tgz",
"resolved": "https://registry.npmjs.org/lodash._baseflatten/-/lodash._baseflatten-3.1.4.tgz",
"dependencies": {
"lodash.isarguments": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
},
"lodash.isarray": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
}
}
},
"lodash._isiterateecall": {
"version": "3.0.9",
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
}
}
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"path-is-absolute": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
},
"readdirp": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/readdirp/-/readdirp-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/readdirp/-/readdirp-2.0.0.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
"graceful-fs": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "4.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
},
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"process-nextick-args": {
"version": "1.0.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"string_decoder": {
"version": "0.10.31",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"util-deprecate": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(package.json): uninstall gulp-watch, install chokidar@^1.0.1
2015-05-12 18:15:49 -04:00
}
}
}
}
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"fsevents": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/fsevents/-/fsevents-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/fsevents/-/fsevents-1.0.2.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"nan": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
"from": "https://registry.npmjs.org/nan/-/nan-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/nan/-/nan-2.1.0.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"node-pre-gyp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.6.12",
"from": "node-pre-gyp@0.6.12",
"resolved": "https://registry.npmjs.org/node-pre-gyp/-/node-pre-gyp-0.6.12.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"nopt": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.4",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "nopt@~3.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/nopt/-/nopt-3.0.4.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"abbrev": {
"version": "1.0.7",
"from": "abbrev@1",
"resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"npmlog": {
"version": "1.2.1",
"from": "npmlog@~1.2.0",
"resolved": "https://registry.npmjs.org/npmlog/-/npmlog-1.2.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"ansi": {
"version": "0.3.0",
"from": "ansi@~0.3.0",
"resolved": "https://registry.npmjs.org/ansi/-/ansi-0.3.0.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"are-we-there-yet": {
"version": "1.0.4",
"from": "are-we-there-yet@~1.0.0",
"resolved": "https://registry.npmjs.org/are-we-there-yet/-/are-we-there-yet-1.0.4.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"delegates": {
"version": "0.1.0",
"from": "delegates@^0.1.0",
"resolved": "https://registry.npmjs.org/delegates/-/delegates-0.1.0.tgz"
},
"readable-stream": {
"version": "1.1.13",
"from": "readable-stream@^1.1.13",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "core-util-is@~1.0.0",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "isarray@0.0.1",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "string_decoder@~0.10.x",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "inherits@2",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
}
}
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"gauge": {
"version": "1.2.2",
"from": "gauge@~1.2.0",
"resolved": "https://registry.npmjs.org/gauge/-/gauge-1.2.2.tgz",
"dependencies": {
"has-unicode": {
"version": "1.0.0",
"from": "has-unicode@^1.0.0",
"resolved": "https://registry.npmjs.org/has-unicode/-/has-unicode-1.0.0.tgz"
},
"lodash.pad": {
"version": "3.1.1",
"from": "lodash.pad@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash.pad/-/lodash.pad-3.1.1.tgz",
"dependencies": {
"lodash._basetostring": {
"version": "3.0.1",
"from": "lodash._basetostring@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._createpadding": {
"version": "3.6.1",
"from": "lodash._createpadding@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash._createpadding/-/lodash._createpadding-3.6.1.tgz",
"dependencies": {
"lodash.repeat": {
"version": "3.0.1",
"from": "lodash.repeat@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash.repeat/-/lodash.repeat-3.0.1.tgz"
}
}
}
}
},
"lodash.padleft": {
"version": "3.1.1",
"from": "lodash.padleft@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash.padleft/-/lodash.padleft-3.1.1.tgz",
"dependencies": {
"lodash._basetostring": {
"version": "3.0.1",
"from": "lodash._basetostring@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._createpadding": {
"version": "3.6.1",
"from": "lodash._createpadding@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash._createpadding/-/lodash._createpadding-3.6.1.tgz",
"dependencies": {
"lodash.repeat": {
"version": "3.0.1",
"from": "lodash.repeat@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash.repeat/-/lodash.repeat-3.0.1.tgz"
}
}
}
}
},
"lodash.padright": {
"version": "3.1.1",
"from": "lodash.padright@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash.padright/-/lodash.padright-3.1.1.tgz",
"dependencies": {
"lodash._basetostring": {
"version": "3.0.1",
"from": "lodash._basetostring@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._createpadding": {
"version": "3.6.1",
"from": "lodash._createpadding@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash._createpadding/-/lodash._createpadding-3.6.1.tgz",
"dependencies": {
"lodash.repeat": {
"version": "3.0.1",
"from": "lodash.repeat@^3.0.0",
"resolved": "https://registry.npmjs.org/lodash.repeat/-/lodash.repeat-3.0.1.tgz"
}
}
}
}
}
}
}
}
},
"request": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.64.0",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "request@2.x",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/request/-/request-2.64.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"bl": {
"version": "1.0.0",
"from": "bl@~1.0.0",
"resolved": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
"dependencies": {
"readable-stream": {
"version": "2.0.2",
"from": "readable-stream@~2.0.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.2.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "core-util-is@~1.0.0",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "inherits@~2.0.1",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "isarray@0.0.1",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.3",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "process-nextick-args@~1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"string_decoder": {
"version": "0.10.31",
"from": "string_decoder@~0.10.x",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.1",
"from": "util-deprecate@~1.0.1",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.1.tgz"
}
}
}
}
},
"caseless": {
"version": "0.11.0",
"from": "caseless@~0.11.0",
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz"
},
"extend": {
"version": "3.0.0",
"from": "extend@~3.0.0",
"resolved": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz"
},
"forever-agent": {
"version": "0.6.1",
"from": "forever-agent@~0.6.0",
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz"
},
"form-data": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0-rc3",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "form-data@~1.0.0-rc1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"async": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.4.2",
"from": "async@^1.4.0",
"resolved": "https://registry.npmjs.org/async/-/async-1.4.2.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
}
}
},
"json-stringify-safe": {
"version": "5.0.1",
"from": "json-stringify-safe@~5.0.0",
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
},
"mime-types": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.7",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "mime-types@~2.1.2",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"mime-db": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.19.0",
"from": "mime-db@~1.19.0",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
}
}
},
"node-uuid": {
"version": "1.4.3",
"from": "node-uuid@~1.4.0",
"resolved": "https://registry.npmjs.org/node-uuid/-/node-uuid-1.4.3.tgz"
},
"qs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.1.0",
"from": "qs@~5.1.0",
"resolved": "https://registry.npmjs.org/qs/-/qs-5.1.0.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"tunnel-agent": {
"version": "0.4.1",
"from": "tunnel-agent@~0.4.0",
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz"
},
"tough-cookie": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "tough-cookie@>=0.12.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.1.0.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"http-signature": {
"version": "0.11.0",
"from": "http-signature@~0.11.0",
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
"dependencies": {
"assert-plus": {
"version": "0.1.5",
"from": "assert-plus@^0.1.5",
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
},
"asn1": {
"version": "0.1.11",
"from": "asn1@0.1.11",
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz"
},
"ctype": {
"version": "0.5.3",
"from": "ctype@0.5.3",
"resolved": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz"
}
}
},
"oauth-sign": {
"version": "0.8.0",
"from": "oauth-sign@~0.8.0",
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz"
},
"hawk": {
"version": "3.1.0",
"from": "hawk@~3.1.0",
"resolved": "https://registry.npmjs.org/hawk/-/hawk-3.1.0.tgz",
"dependencies": {
"hoek": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.16.3",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "hoek@2.x.x",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"boom": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.9.0",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "boom@^2.8.x",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/boom/-/boom-2.9.0.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"cryptiles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.5",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "cryptiles@2.x.x",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"sntp": {
"version": "1.0.9",
"from": "sntp@1.x.x",
"resolved": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz"
}
}
},
"aws-sign2": {
"version": "0.5.0",
"from": "aws-sign2@~0.5.0",
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.5.0.tgz"
},
"stringstream": {
"version": "0.0.4",
"from": "stringstream@~0.0.4",
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.4.tgz"
},
"combined-stream": {
"version": "1.0.5",
"from": "combined-stream@~1.0.1",
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
"dependencies": {
"delayed-stream": {
"version": "1.0.0",
"from": "delayed-stream@~1.0.0",
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz"
}
}
},
"isstream": {
"version": "0.1.2",
"from": "isstream@~0.1.1",
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
},
"har-validator": {
"version": "1.8.0",
"from": "har-validator@^1.6.1",
"resolved": "https://registry.npmjs.org/har-validator/-/har-validator-1.8.0.tgz",
"dependencies": {
"bluebird": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.10.2",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "bluebird@^2.9.30",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/bluebird/-/bluebird-2.10.2.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"chalk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "chalk@^1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"ansi-styles": {
"version": "2.1.0",
"from": "ansi-styles@^2.1.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
"from": "escape-string-regexp@^1.0.2",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "2.0.0",
"from": "has-ansi@^2.0.0",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "ansi-regex@^2.0.0",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
"from": "strip-ansi@^3.0.0",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "ansi-regex@^2.0.0",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"supports-color": {
"version": "2.0.0",
"from": "supports-color@^2.0.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
}
}
},
"commander": {
"version": "2.8.1",
"from": "commander@^2.8.1",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.8.1.tgz",
"dependencies": {
"graceful-readlink": {
"version": "1.0.1",
"from": "graceful-readlink@>= 1.0.0",
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz"
}
}
},
"is-my-json-valid": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.12.2",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "is-my-json-valid@^2.12.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"generate-function": {
"version": "2.0.0",
"from": "generate-function@^2.0.0",
"resolved": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz"
},
"generate-object-property": {
"version": "1.2.0",
"from": "generate-object-property@^1.1.0",
"resolved": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
"dependencies": {
"is-property": {
"version": "1.0.2",
"from": "is-property@^1.0.0",
"resolved": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz"
}
}
},
"jsonpointer": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "jsonpointer@2.0.0",
"resolved": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"xtend": {
"version": "4.0.0",
"from": "xtend@^4.0.0",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.0.tgz"
}
}
}
}
}
}
},
"semver": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.3",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "semver@~5.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"tar": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.1",
"from": "tar@~2.2.0",
"resolved": "https://registry.npmjs.org/tar/-/tar-2.2.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"block-stream": {
"version": "0.0.8",
"from": "block-stream@*",
"resolved": "https://registry.npmjs.org/block-stream/-/block-stream-0.0.8.tgz"
},
"fstream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.8",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "fstream@^1.0.2",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/fstream/-/fstream-1.0.8.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"graceful-fs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.1.2",
"from": "graceful-fs@^4.1.2",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
}
}
},
"inherits": {
"version": "2.0.1",
"from": "inherits@2",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"tar-pack": {
"version": "2.0.0",
"from": "tar-pack@~2.0.0",
"resolved": "https://registry.npmjs.org/tar-pack/-/tar-pack-2.0.0.tgz",
"dependencies": {
"uid-number": {
"version": "0.0.3",
"from": "uid-number@0.0.3",
"resolved": "https://registry.npmjs.org/uid-number/-/uid-number-0.0.3.tgz"
},
"once": {
"version": "1.1.1",
"from": "once@~1.1.1",
"resolved": "https://registry.npmjs.org/once/-/once-1.1.1.tgz"
},
"debug": {
"version": "0.7.4",
"from": "debug@~0.7.2",
"resolved": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz"
},
"rimraf": {
"version": "2.2.8",
"from": "rimraf@~2.2.0",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz"
},
"fstream": {
"version": "0.1.31",
"from": "fstream@~0.1.22",
"resolved": "https://registry.npmjs.org/fstream/-/fstream-0.1.31.tgz",
"dependencies": {
"graceful-fs": {
"version": "3.0.8",
"from": "graceful-fs@~3.0.2",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "inherits@~2.0.0",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"tar": {
"version": "0.1.20",
"from": "tar@~0.1.17",
"resolved": "https://registry.npmjs.org/tar/-/tar-0.1.20.tgz",
"dependencies": {
"block-stream": {
"version": "0.0.8",
"from": "block-stream@*",
"resolved": "https://registry.npmjs.org/block-stream/-/block-stream-0.0.8.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "inherits@2",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"fstream-ignore": {
"version": "0.0.7",
"from": "fstream-ignore@0.0.7",
"resolved": "https://registry.npmjs.org/fstream-ignore/-/fstream-ignore-0.0.7.tgz",
"dependencies": {
"minimatch": {
"version": "0.2.14",
"from": "minimatch@~0.2.0",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.2.14.tgz",
"dependencies": {
"lru-cache": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.7.0",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "lru-cache@2",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"sigmund": {
"version": "1.0.1",
"from": "sigmund@~1.0.0",
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "inherits@~2.0.1",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"readable-stream": {
"version": "1.0.33",
"from": "readable-stream@~1.0.2",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "core-util-is@~1.0.0",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "isarray@0.0.1",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "string_decoder@~0.10.x",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "inherits@~2.0.1",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"graceful-fs": {
"version": "1.2.3",
"from": "graceful-fs@1.2",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-1.2.3.tgz"
}
}
},
"mkdirp": {
"version": "0.5.1",
"from": "mkdirp@~0.5.0",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
"from": "minimist@0.0.8",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
},
"rc": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.2",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "rc@~1.1.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/rc/-/rc-1.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"minimist": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.0",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "minimist@^1.1.2",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"deep-extend": {
"version": "0.2.11",
"from": "deep-extend@~0.2.5",
"resolved": "https://registry.npmjs.org/deep-extend/-/deep-extend-0.2.11.tgz"
},
"strip-json-comments": {
"version": "0.1.3",
"from": "strip-json-comments@0.1.x",
"resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-0.1.3.tgz"
},
"ini": {
"version": "1.3.4",
"from": "ini@~1.3.0",
"resolved": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz"
}
}
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "rimraf@~2.4.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"glob": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.15",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "glob@^5.0.14",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "inflight@^1.0.4",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "wrappy@1",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "inherits@~2.0.1",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"minimatch": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.0",
"from": "minimatch@2 || 3",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"brace-expansion": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"from": "brace-expansion@^1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"balanced-match": {
"version": "0.2.0",
"from": "balanced-match@^0.2.0",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.0.tgz"
},
"concat-map": {
"version": "0.0.1",
"from": "concat-map@0.0.1",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
}
}
}
}
},
"once": {
"version": "1.3.2",
"from": "once@^1.3.0",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "wrappy@1",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "path-is-absolute@^1.0.0",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
}
}
}
}
}
}
},
"clang-format": {
feat: upgrade clang-format to 1.0.32.
2015-10-20 05:10:31 -04:00
"version": "1.0.32",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/clang-format/-/clang-format-1.0.32.tgz",
feat: upgrade clang-format to 1.0.32.
2015-10-20 05:10:31 -04:00
"resolved": "https://registry.npmjs.org/clang-format/-/clang-format-1.0.32.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"resolve": {
"version": "1.1.6",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/resolve/-/resolve-1.1.6.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.1.6.tgz"
}
}
},
"conventional-changelog": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/conventional-changelog/-/conventional-changelog-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/conventional-changelog/-/conventional-changelog-0.2.1.tgz",
"dependencies": {
"add-stream": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/add-stream/-/add-stream-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/add-stream/-/add-stream-1.0.0.tgz"
},
"compare-func": {
"version": "1.3.1",
"from": "https://registry.npmjs.org/compare-func/-/compare-func-1.3.1.tgz",
"resolved": "https://registry.npmjs.org/compare-func/-/compare-func-1.3.1.tgz",
"dependencies": {
"array-ify": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/array-ify/-/array-ify-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/array-ify/-/array-ify-1.0.0.tgz"
},
"dot-prop": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/dot-prop/-/dot-prop-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/dot-prop/-/dot-prop-2.2.0.tgz"
}
}
},
"conventional-changelog-writer": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/conventional-changelog-writer/-/conventional-changelog-writer-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/conventional-changelog-writer/-/conventional-changelog-writer-0.2.1.tgz",
"dependencies": {
"conventional-commits-filter": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.1",
"from": "https://registry.npmjs.org/conventional-commits-filter/-/conventional-commits-filter-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/conventional-commits-filter/-/conventional-commits-filter-0.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"is-subset": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/is-subset/-/is-subset-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/is-subset/-/is-subset-0.1.1.tgz"
},
"modify-values": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/modify-values/-/modify-values-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/modify-values/-/modify-values-1.0.0.tgz"
}
}
},
"handlebars": {
"version": "3.0.3",
"from": "https://registry.npmjs.org/handlebars/-/handlebars-3.0.3.tgz",
"resolved": "https://registry.npmjs.org/handlebars/-/handlebars-3.0.3.tgz",
"dependencies": {
"optimist": {
"version": "0.6.1",
"from": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
"dependencies": {
"wordwrap": {
"version": "0.0.3",
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
},
"minimist": {
"version": "0.0.10",
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz"
}
}
},
"source-map": {
"version": "0.1.43",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.1.43.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.43.tgz",
"dependencies": {
"amdefine": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
}
}
},
"uglify-js": {
"version": "2.3.6",
"from": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.3.6.tgz",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.3.6.tgz",
"dependencies": {
"async": {
"version": "0.2.10",
"from": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
},
"optimist": {
"version": "0.3.7",
"from": "https://registry.npmjs.org/optimist/-/optimist-0.3.7.tgz",
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.3.7.tgz",
"dependencies": {
"wordwrap": {
"version": "0.0.3",
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
}
}
}
}
}
}
},
"split": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/split/-/split-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/split/-/split-1.0.0.tgz",
"dependencies": {
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"through": {
"version": "2.3.8",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
}
}
}
}
},
"conventional-commits-parser": {
"version": "0.0.19",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/conventional-commits-parser/-/conventional-commits-parser-0.0.19.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/conventional-commits-parser/-/conventional-commits-parser-0.0.19.tgz",
"dependencies": {
"JSONStream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.6",
"from": "https://registry.npmjs.org/JSONStream/-/JSONStream-1.0.6.tgz",
"resolved": "https://registry.npmjs.org/JSONStream/-/JSONStream-1.0.6.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"dependencies": {
"jsonparse": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.0",
"from": "https://registry.npmjs.org/jsonparse/-/jsonparse-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/jsonparse/-/jsonparse-1.2.0.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
},
"through": {
"version": "2.3.8",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
}
}
},
"is-text-path": {
"version": "1.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/is-text-path/-/is-text-path-1.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/is-text-path/-/is-text-path-1.0.1.tgz",
"dependencies": {
"text-extensions": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.3.3",
"from": "https://registry.npmjs.org/text-extensions/-/text-extensions-1.3.3.tgz",
"resolved": "https://registry.npmjs.org/text-extensions/-/text-extensions-1.3.3.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
}
}
},
"split": {
"version": "1.0.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/split/-/split-1.0.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/split/-/split-1.0.0.tgz",
"dependencies": {
"through": {
"version": "2.3.8",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
}
}
}
}
},
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"dateformat": {
"version": "1.0.11",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
}
}
},
"get-pkg-repo": {
"version": "0.1.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/get-pkg-repo/-/get-pkg-repo-0.1.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/get-pkg-repo/-/get-pkg-repo-0.1.0.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
},
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"normalize-package-data": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"validate-npm-package-license": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"dependencies": {
"spdx-license-ids": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"spdx-expression-parse": {
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
}
}
}
}
}
}
},
"git-raw-commits": {
"version": "0.1.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/git-raw-commits/-/git-raw-commits-0.1.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/git-raw-commits/-/git-raw-commits-0.1.0.tgz",
"dependencies": {
"dargs": {
"version": "4.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/dargs/-/dargs-4.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/dargs/-/dargs-4.0.1.tgz",
"dependencies": {
"number-is-nan": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.0.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
},
"lodash.template": {
"version": "3.6.2",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"dependencies": {
"lodash._basecopy": {
"version": "3.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
},
"lodash._basetostring": {
"version": "3.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._basevalues": {
"version": "3.0.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
"version": "3.0.9",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.escape": {
"version": "3.0.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
},
"lodash.keys": {
"version": "3.1.2",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"dependencies": {
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"lodash._getnative": {
"version": "3.9.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
},
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"lodash.isarguments": {
"version": "3.0.4",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
},
"lodash.isarray": {
"version": "3.0.4",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
}
}
},
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"lodash.restparam": {
"version": "3.6.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
},
"lodash.templatesettings": {
"version": "3.1.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
}
}
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
},
"split2": {
"version": "1.0.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/split2/-/split2-1.0.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/split2/-/split2-1.0.0.tgz"
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
}
}
},
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"git-semver-tags": {
"version": "1.0.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/git-semver-tags/-/git-semver-tags-1.0.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/git-semver-tags/-/git-semver-tags-1.0.0.tgz"
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
},
"lodash": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.10.1",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
},
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"meow": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"dependencies": {
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"camelcase-keys": {
"version": "1.0.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
},
"map-obj": {
"version": "1.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
},
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"object-assign": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
}
}
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
}
}
},
"semver": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.3",
"from": "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz",
"resolved": "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
},
"tempfile": {
"version": "1.1.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/tempfile/-/tempfile-1.1.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/tempfile/-/tempfile-1.1.1.tgz",
"dependencies": {
"os-tmpdir": {
"version": "1.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz"
},
"uuid": {
"version": "2.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/uuid/-/uuid-2.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/uuid/-/uuid-2.0.1.tgz"
}
}
},
"through2": {
"version": "2.0.0",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"dependencies": {
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
},
"string_decoder": {
"version": "0.10.31",
chore(build): Upgrade to TypeScript@1.5.3 This change also makes us compliant with 1.6.0-dev compiler, so we can do some experiments with apps that use 1.6 features and compile against Angular. We should probably add a travis build for 1.6 so we stay compatible with both versions.
2015-07-29 23:09:54 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(changelog): update to new changelog package. Regen-ed the CHANGELOG.md (for consistency). Seems like some old commits are not present in new the CHANGELOG.md, but it doesn't seem worthy of further investigation. closes #3204, #3172
2015-07-29 16:44:39 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
}
}
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"del": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.1",
"from": "https://registry.npmjs.org/del/-/del-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/del/-/del-1.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"each-async": {
"version": "1.1.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/each-async/-/each-async-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/each-async/-/each-async-1.1.1.tgz",
"dependencies": {
"onetime": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/onetime/-/onetime-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/onetime/-/onetime-1.0.0.tgz"
},
"set-immediate-shim": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/set-immediate-shim/-/set-immediate-shim-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/set-immediate-shim/-/set-immediate-shim-1.0.1.tgz"
}
}
},
"globby": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
"from": "https://registry.npmjs.org/globby/-/globby-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/globby/-/globby-2.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"array-union": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/array-union/-/array-union-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/array-union/-/array-union-1.0.1.tgz",
"dependencies": {
"array-uniq": {
"version": "1.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
}
}
},
"async": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.5.0",
"from": "https://registry.npmjs.org/async/-/async-1.5.0.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-1.5.0.tgz"
},
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"is-path-cwd": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/is-path-cwd/-/is-path-cwd-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/is-path-cwd/-/is-path-cwd-1.0.0.tgz"
},
"is-path-in-cwd": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/is-path-in-cwd/-/is-path-in-cwd-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/is-path-in-cwd/-/is-path-in-cwd-1.0.0.tgz",
"dependencies": {
"is-path-inside": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/is-path-inside/-/is-path-inside-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/is-path-inside/-/is-path-inside-1.0.0.tgz",
"dependencies": {
"path-is-inside": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/path-is-inside/-/path-is-inside-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/path-is-inside/-/path-is-inside-1.0.1.tgz"
}
}
}
}
},
"object-assign": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"dependencies": {
"glob": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"inherits": {
"version": "2.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
}
}
},
"es6-shim": {
"version": "0.33.10",
"from": "https://registry.npmjs.org/es6-shim/-/es6-shim-0.33.10.tgz",
"resolved": "https://registry.npmjs.org/es6-shim/-/es6-shim-0.33.10.tgz"
},
"firefox-profile": {
"version": "0.3.11",
"from": "https://registry.npmjs.org/firefox-profile/-/firefox-profile-0.3.11.tgz",
"resolved": "https://registry.npmjs.org/firefox-profile/-/firefox-profile-0.3.11.tgz",
"dependencies": {
"adm-zip": {
"version": "0.4.7",
"from": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.7.tgz",
"resolved": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.7.tgz"
},
"archiver": {
"version": "0.14.4",
"from": "https://registry.npmjs.org/archiver/-/archiver-0.14.4.tgz",
"resolved": "https://registry.npmjs.org/archiver/-/archiver-0.14.4.tgz",
"dependencies": {
"buffer-crc32": {
"version": "0.2.5",
"from": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.5.tgz",
"resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.5.tgz"
},
"glob": {
"version": "4.3.5",
"from": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash": {
"version": "3.2.0",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.2.0.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.2.0.tgz"
},
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"readable-stream": {
"version": "1.0.33",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"tar-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.5",
"from": "https://registry.npmjs.org/tar-stream/-/tar-stream-1.1.5.tgz",
"resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-1.1.5.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"dependencies": {
"bl": {
"version": "0.9.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz"
},
"end-of-stream": {
"version": "1.1.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz",
"dependencies": {
"once": {
"version": "1.3.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
},
"zip-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.2",
"from": "https://registry.npmjs.org/zip-stream/-/zip-stream-0.5.2.tgz",
"resolved": "https://registry.npmjs.org/zip-stream/-/zip-stream-0.5.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"dependencies": {
"compress-commons": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.2.9",
"from": "https://registry.npmjs.org/compress-commons/-/compress-commons-0.2.9.tgz",
"resolved": "https://registry.npmjs.org/compress-commons/-/compress-commons-0.2.9.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"dependencies": {
"crc32-stream": {
"version": "0.3.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz"
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"node-int64": {
"version": "0.3.3",
"from": "https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz",
"resolved": "https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
}
}
}
}
},
"async": {
"version": "0.9.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.9.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
},
"fs-extra": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.16.5",
"from": "https://registry.npmjs.org/fs-extra/-/fs-extra-0.16.5.tgz",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-0.16.5.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"graceful-fs": {
"version": "3.0.8",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
},
"jsonfile": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.3",
"from": "https://registry.npmjs.org/jsonfile/-/jsonfile-2.2.3.tgz",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-2.2.3.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ini": {
"version": "1.3.4",
"from": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz",
"resolved": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz"
},
"jetpack-id": {
"version": "0.0.4",
"from": "https://registry.npmjs.org/jetpack-id/-/jetpack-id-0.0.4.tgz",
"resolved": "https://registry.npmjs.org/jetpack-id/-/jetpack-id-0.0.4.tgz"
},
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"lazystream": {
"version": "0.1.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/lazystream/-/lazystream-0.1.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/lazystream/-/lazystream-0.1.0.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.5.0.tgz"
},
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"wrench": {
"version": "1.5.8",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/wrench/-/wrench-1.5.8.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/wrench/-/wrench-1.5.8.tgz"
},
"xml2js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.15",
"from": "https://registry.npmjs.org/xml2js/-/xml2js-0.4.15.tgz",
"resolved": "https://registry.npmjs.org/xml2js/-/xml2js-0.4.15.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"dependencies": {
"sax": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.4",
"from": "https://registry.npmjs.org/sax/-/sax-1.1.4.tgz",
"resolved": "https://registry.npmjs.org/sax/-/sax-1.1.4.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
},
"xmlbuilder": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-4.0.0.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"fs-extra": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.18.4",
"from": "https://registry.npmjs.org/fs-extra/-/fs-extra-0.18.4.tgz",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-0.18.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"graceful-fs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.8",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"jsonfile": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.3",
"from": "https://registry.npmjs.org/jsonfile/-/jsonfile-2.2.3.tgz",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-2.2.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"glob": {
"version": "4.5.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-4.5.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-4.5.3.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
},
"googleapis": {
"version": "1.0.23",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/googleapis/-/googleapis-1.0.23.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/googleapis/-/googleapis-1.0.23.tgz",
"dependencies": {
"async": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.9.2",
"from": "https://registry.npmjs.org/async/-/async-0.9.2.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"gapitoken": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.5",
"from": "https://registry.npmjs.org/gapitoken/-/gapitoken-0.1.5.tgz",
"resolved": "https://registry.npmjs.org/gapitoken/-/gapitoken-0.1.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"jws": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.0",
"from": "https://registry.npmjs.org/jws/-/jws-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/jws/-/jws-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"jwa": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/jwa/-/jwa-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/jwa/-/jwa-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"base64url": {
"version": "0.0.6",
"from": "https://registry.npmjs.org/base64url/-/base64url-0.0.6.tgz",
"resolved": "https://registry.npmjs.org/base64url/-/base64url-0.0.6.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"buffer-equal-constant-time": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/buffer-equal-constant-time/-/buffer-equal-constant-time-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/buffer-equal-constant-time/-/buffer-equal-constant-time-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ecdsa-sig-formatter": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/ecdsa-sig-formatter/-/ecdsa-sig-formatter-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/ecdsa-sig-formatter/-/ecdsa-sig-formatter-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"asn1.js": {
"version": "2.2.1",
"from": "https://registry.npmjs.org/asn1.js/-/asn1.js-2.2.1.tgz",
"resolved": "https://registry.npmjs.org/asn1.js/-/asn1.js-2.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"bn.js": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/bn.js/-/bn.js-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/bn.js/-/bn.js-2.2.0.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"minimalistic-assert": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"base64-url": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/base64-url/-/base64-url-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/base64-url/-/base64-url-1.2.1.tgz"
}
}
}
}
},
"base64url": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/base64url/-/base64url-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/base64url/-/base64url-1.0.4.tgz",
"dependencies": {
"concat-stream": {
"version": "1.4.10",
"from": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.4.10.tgz",
"resolved": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.4.10.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"typedarray": {
"version": "0.0.6",
"from": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz",
"resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz"
},
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"meow": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/meow/-/meow-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"camelcase-keys": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
"indent-string": {
"version": "1.2.2",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-1.2.2.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-1.2.2.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
},
"repeating": {
"version": "1.1.3",
"from": "https://registry.npmjs.org/repeating/-/repeating-1.1.3.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-1.1.3.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
"request": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.65.0",
"from": "https://registry.npmjs.org/request/-/request-2.65.0.tgz",
"resolved": "https://registry.npmjs.org/request/-/request-2.65.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"bl": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
"caseless": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.11.0",
"from": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz",
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz"
},
"extend": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"forever-agent": {
"version": "0.6.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz"
},
"form-data": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0-rc3",
"from": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
"resolved": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
"dependencies": {
"async": {
"version": "1.5.0",
"from": "https://registry.npmjs.org/async/-/async-1.5.0.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-1.5.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"json-stringify-safe": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.1",
"from": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"mime-types": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.7",
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"mime-db": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.19.0",
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"qs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.2.0",
"from": "https://registry.npmjs.org/qs/-/qs-5.2.0.tgz",
"resolved": "https://registry.npmjs.org/qs/-/qs-5.2.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"tunnel-agent": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.1",
"from": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz",
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"tough-cookie": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.0",
"from": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"http-signature": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.11.0",
"from": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"assert-plus": {
"version": "0.1.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
},
"asn1": {
"version": "0.1.11",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz"
},
"ctype": {
"version": "0.5.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz"
}
}
},
"oauth-sign": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.8.0",
"from": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz",
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"hawk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.1.0",
"from": "https://registry.npmjs.org/hawk/-/hawk-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/hawk/-/hawk-3.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"hoek": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.16.3",
"from": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz",
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"boom": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.10.1",
"from": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz",
"resolved": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"cryptiles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.5",
"from": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz",
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"sntp": {
"version": "1.0.9",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz"
}
}
},
"aws-sign2": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.6.0",
"from": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.6.0.tgz",
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.6.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"stringstream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.0.5",
"from": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"combined-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.5",
"from": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"delayed-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"isstream": {
"version": "0.1.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
},
"har-validator": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.2",
"from": "https://registry.npmjs.org/har-validator/-/har-validator-2.0.2.tgz",
"resolved": "https://registry.npmjs.org/har-validator/-/har-validator-2.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"chalk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-styles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"escape-string-regexp": {
"version": "1.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"supports-color": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"commander": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.9.0",
"from": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"graceful-readlink": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz"
}
}
},
"is-my-json-valid": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.12.2",
"from": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
"resolved": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"generate-function": {
"version": "2.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz"
},
"generate-object-property": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.0",
"from": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"is-property": {
"version": "1.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz"
}
}
},
"jsonpointer": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz"
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
}
}
},
"request": {
"version": "2.51.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/request/-/request-2.51.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/request/-/request-2.51.0.tgz",
"dependencies": {
"bl": {
"version": "0.9.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
},
"caseless": {
"version": "0.8.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/caseless/-/caseless-0.8.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.8.0.tgz"
},
"forever-agent": {
"version": "0.5.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.5.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.5.2.tgz"
},
"form-data": {
"version": "0.2.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/form-data/-/form-data-0.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/form-data/-/form-data-0.2.0.tgz",
"dependencies": {
"mime-types": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.14",
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"mime-db": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.12.0",
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"json-stringify-safe": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.1",
"from": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"mime-types": {
"version": "1.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/mime-types/-/mime-types-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-1.0.2.tgz"
},
"qs": {
"version": "2.3.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/qs/-/qs-2.3.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/qs/-/qs-2.3.3.tgz"
},
"tunnel-agent": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.1",
"from": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz",
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"tough-cookie": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.0",
"from": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"http-signature": {
"version": "0.10.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz",
"dependencies": {
"assert-plus": {
"version": "0.1.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
},
"asn1": {
"version": "0.1.11",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz"
},
"ctype": {
"version": "0.5.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz"
}
}
},
"oauth-sign": {
"version": "0.5.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.5.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.5.0.tgz"
},
"hawk": {
"version": "1.1.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/hawk/-/hawk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/hawk/-/hawk-1.1.1.tgz",
"dependencies": {
"hoek": {
"version": "0.9.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/hoek/-/hoek-0.9.1.tgz"
},
"boom": {
"version": "0.4.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/boom/-/boom-0.4.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/boom/-/boom-0.4.2.tgz"
},
"cryptiles": {
"version": "0.2.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-0.2.2.tgz"
},
"sntp": {
"version": "0.2.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/sntp/-/sntp-0.2.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/sntp/-/sntp-0.2.4.tgz"
}
}
},
"aws-sign2": {
"version": "0.5.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.5.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.5.0.tgz"
},
"stringstream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.0.5",
"from": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"combined-stream": {
"version": "0.0.7",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/combined-stream/-/combined-stream-0.0.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-0.0.7.tgz",
"dependencies": {
"delayed-stream": {
"version": "0.0.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-0.0.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-0.0.5.tgz"
}
}
}
}
},
"string-template": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "0.2.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string-template/-/string-template-0.2.1.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/string-template/-/string-template-0.2.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"gulp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.9.0",
"from": "https://registry.npmjs.org/gulp/-/gulp-3.9.0.tgz",
"resolved": "https://registry.npmjs.org/gulp/-/gulp-3.9.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"archy": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/archy/-/archy-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/archy/-/archy-1.0.0.tgz"
},
"chalk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-styles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"escape-string-regexp": {
"version": "1.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"strip-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"supports-color": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"deprecated": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/deprecated/-/deprecated-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/deprecated/-/deprecated-0.0.1.tgz"
},
"gulp-util": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.7",
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"array-differ": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
},
"array-uniq": {
"version": "1.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
},
"beeper": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.0",
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"dateformat": {
"version": "1.0.11",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"meow": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"map-obj": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"fancy-log": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulplog": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glogg": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"has-gulplog": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "0.1.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._reescape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.template": {
"version": "3.6.2",
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._basecopy": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._basetostring": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._basevalues": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
"version": "3.0.9",
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
},
"lodash.escape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
},
"lodash.keys": {
"version": "3.1.2",
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._getnative": {
"version": "3.9.1",
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
},
"lodash.isarguments": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
},
"lodash.isarray": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.restparam": {
"version": "3.6.1",
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
},
"lodash.templatesettings": {
"version": "3.1.0",
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"multipipe": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"duplexer2": {
"version": "0.0.2",
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"replace-ext": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"through2": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"vinyl": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
}
}
},
"interpret": {
"version": "0.6.6",
"from": "https://registry.npmjs.org/interpret/-/interpret-0.6.6.tgz",
"resolved": "https://registry.npmjs.org/interpret/-/interpret-0.6.6.tgz"
},
"liftoff": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/liftoff/-/liftoff-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/liftoff/-/liftoff-2.2.0.tgz",
"dependencies": {
"extend": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/extend/-/extend-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/extend/-/extend-2.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"findup-sync": {
"version": "0.3.0",
"from": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.3.0.tgz",
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"wrappy": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"flagged-respawn": {
"version": "0.3.1",
"from": "https://registry.npmjs.org/flagged-respawn/-/flagged-respawn-0.3.1.tgz",
"resolved": "https://registry.npmjs.org/flagged-respawn/-/flagged-respawn-0.3.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"rechoir": {
"version": "0.6.2",
"from": "https://registry.npmjs.org/rechoir/-/rechoir-0.6.2.tgz",
"resolved": "https://registry.npmjs.org/rechoir/-/rechoir-0.6.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolve": {
"version": "1.1.6",
"from": "https://registry.npmjs.org/resolve/-/resolve-1.1.6.tgz",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.1.6.tgz"
}
}
},
"orchestrator": {
"version": "0.3.7",
"from": "https://registry.npmjs.org/orchestrator/-/orchestrator-0.3.7.tgz",
"resolved": "https://registry.npmjs.org/orchestrator/-/orchestrator-0.3.7.tgz",
"dependencies": {
"end-of-stream": {
"version": "0.1.5",
"from": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-0.1.5.tgz",
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-0.1.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sequencify": {
"version": "0.0.7",
"from": "https://registry.npmjs.org/sequencify/-/sequencify-0.0.7.tgz",
"resolved": "https://registry.npmjs.org/sequencify/-/sequencify-0.0.7.tgz"
},
"stream-consume": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/stream-consume/-/stream-consume-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/stream-consume/-/stream-consume-0.1.0.tgz"
}
}
},
"pretty-hrtime": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/pretty-hrtime/-/pretty-hrtime-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/pretty-hrtime/-/pretty-hrtime-1.0.1.tgz"
},
"tildify": {
"version": "1.1.2",
"from": "https://registry.npmjs.org/tildify/-/tildify-1.1.2.tgz",
"resolved": "https://registry.npmjs.org/tildify/-/tildify-1.1.2.tgz",
"dependencies": {
"os-homedir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz"
}
}
},
"v8flags": {
"version": "2.0.10",
"from": "https://registry.npmjs.org/v8flags/-/v8flags-2.0.10.tgz",
"resolved": "https://registry.npmjs.org/v8flags/-/v8flags-2.0.10.tgz",
"dependencies": {
"user-home": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/user-home/-/user-home-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/user-home/-/user-home-1.1.1.tgz"
}
}
},
"vinyl-fs": {
"version": "0.3.14",
"from": "https://registry.npmjs.org/vinyl-fs/-/vinyl-fs-0.3.14.tgz",
"resolved": "https://registry.npmjs.org/vinyl-fs/-/vinyl-fs-0.3.14.tgz",
"dependencies": {
"defaults": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/defaults/-/defaults-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/defaults/-/defaults-1.0.3.tgz",
"dependencies": {
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
}
}
},
"glob-stream": {
"version": "3.1.18",
"from": "https://registry.npmjs.org/glob-stream/-/glob-stream-3.1.18.tgz",
"resolved": "https://registry.npmjs.org/glob-stream/-/glob-stream-3.1.18.tgz",
"dependencies": {
"ordered-read-streams": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/ordered-read-streams/-/ordered-read-streams-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/ordered-read-streams/-/ordered-read-streams-0.1.0.tgz"
},
"glob2base": {
"version": "0.0.12",
"from": "https://registry.npmjs.org/glob2base/-/glob2base-0.0.12.tgz",
"resolved": "https://registry.npmjs.org/glob2base/-/glob2base-0.0.12.tgz",
"dependencies": {
"find-index": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/find-index/-/find-index-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/find-index/-/find-index-0.1.1.tgz"
}
}
},
"unique-stream": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/unique-stream/-/unique-stream-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/unique-stream/-/unique-stream-1.0.0.tgz"
}
}
},
"glob-watcher": {
"version": "0.0.6",
"from": "https://registry.npmjs.org/glob-watcher/-/glob-watcher-0.0.6.tgz",
"resolved": "https://registry.npmjs.org/glob-watcher/-/glob-watcher-0.0.6.tgz",
"dependencies": {
"gaze": {
"version": "0.5.2",
"from": "https://registry.npmjs.org/gaze/-/gaze-0.5.2.tgz",
"resolved": "https://registry.npmjs.org/gaze/-/gaze-0.5.2.tgz",
"dependencies": {
"globule": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/globule/-/globule-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/globule/-/globule-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glob": {
"version": "3.1.21",
"from": "https://registry.npmjs.org/glob/-/glob-3.1.21.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-3.1.21.tgz",
"dependencies": {
"graceful-fs": {
"version": "1.2.3",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-1.2.3.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-1.2.3.tgz"
},
"inherits": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/inherits/-/inherits-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-1.0.2.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"minimatch": {
"version": "0.2.14",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-0.2.14.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.2.14.tgz",
"dependencies": {
"lru-cache": {
"version": "2.7.0",
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz"
},
"sigmund": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"graceful-fs": {
"version": "3.0.8",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"mkdirp": {
"version": "0.5.1",
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"minimist": {
"version": "0.0.8",
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-bom": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-1.0.0.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"first-chunk-stream": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/first-chunk-stream/-/first-chunk-stream-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/first-chunk-stream/-/first-chunk-stream-1.0.0.tgz"
},
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
},
"vinyl": {
"version": "0.4.6",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.4.6.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.4.6.tgz",
"dependencies": {
"clone": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/clone/-/clone-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-0.2.0.tgz"
},
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulp-autoprefixer": {
"version": "3.1.0",
"from": "https://registry.npmjs.org/gulp-autoprefixer/-/gulp-autoprefixer-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/gulp-autoprefixer/-/gulp-autoprefixer-3.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"autoprefixer": {
"version": "6.0.3",
"from": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-6.0.3.tgz",
"resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-6.0.3.tgz",
"dependencies": {
"num2fraction": {
"version": "1.2.2",
"from": "https://registry.npmjs.org/num2fraction/-/num2fraction-1.2.2.tgz",
"resolved": "https://registry.npmjs.org/num2fraction/-/num2fraction-1.2.2.tgz"
},
"browserslist": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/browserslist/-/browserslist-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/browserslist/-/browserslist-1.0.1.tgz"
},
"caniuse-db": {
"version": "1.0.30000356",
"from": "https://registry.npmjs.org/caniuse-db/-/caniuse-db-1.0.30000356.tgz",
"resolved": "https://registry.npmjs.org/caniuse-db/-/caniuse-db-1.0.30000356.tgz"
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"gulp-util": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.7",
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"array-differ": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
},
"array-uniq": {
"version": "1.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
},
"beeper": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.0",
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"chalk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-styles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"escape-string-regexp": {
"version": "1.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-ansi": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "3.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"supports-color": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"dateformat": {
"version": "1.0.11",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"meow": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"map-obj": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.0.1",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): update gulp-clang-format to v1.0.19 Closes #2338
2015-06-04 13:17:34 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
feat: upgrade clang-format and gulp-clang-format. This makes sure just running clang-format will use whatever version is used in the project, by loading it from the closest node_modules folder. It also moves the clang-format dependency to the top and explicitly passes it to gulp-clang-format, giving us more control over the version used.
2015-06-25 19:21:43 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
feat: upgrade clang-format and gulp-clang-format. This makes sure just running clang-format will use whatever version is used in the project, by loading it from the closest node_modules folder. It also moves the clang-format dependency to the top and explicitly passes it to gulp-clang-format, giving us more control over the version used.
2015-06-25 19:21:43 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"read-pkg-up": {
feat: upgrade clang-format and gulp-clang-format. This makes sure just running clang-format will use whatever version is used in the project, by loading it from the closest node_modules folder. It also moves the clang-format dependency to the top and explicitly passes it to gulp-clang-format, giving us more control over the version used.
2015-06-25 19:21:43 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
feat: upgrade clang-format and gulp-clang-format. This makes sure just running clang-format will use whatever version is used in the project, by loading it from the closest node_modules folder. It also moves the clang-format dependency to the top and explicitly passes it to gulp-clang-format, giving us more control over the version used.
2015-06-25 19:21:43 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
}
}
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
}
feat: upgrade clang-format and gulp-clang-format. This makes sure just running clang-format will use whatever version is used in the project, by loading it from the closest node_modules folder. It also moves the clang-format dependency to the top and explicitly passes it to gulp-clang-format, giving us more control over the version used.
2015-06-25 19:21:43 -04:00
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"fancy-log": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulplog": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glogg": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"has-gulplog": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"lodash._reescape": {
"version": "3.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.template": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.6.2",
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"lodash._basecopy": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "3.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash._basetostring": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash._basevalues": {
"version": "3.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.9",
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash.escape": {
"version": "3.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
},
"lodash.keys": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.1.2",
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._getnative": {
"version": "3.9.1",
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"lodash.isarguments": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash.isarray": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"lodash.restparam": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "3.6.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash.templatesettings": {
"version": "3.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
}
}
},
"multipipe": {
"version": "0.1.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
},
"object-assign": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"replace-ext": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"vinyl": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"dependencies": {
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"postcss": {
"version": "5.0.10",
"from": "https://registry.npmjs.org/postcss/-/postcss-5.0.10.tgz",
"resolved": "https://registry.npmjs.org/postcss/-/postcss-5.0.10.tgz",
"dependencies": {
"supports-color": {
"version": "3.1.2",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-3.1.2.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-3.1.2.tgz",
"dependencies": {
"has-flag": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/has-flag/-/has-flag-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-1.0.0.tgz"
}
}
},
"source-map": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
},
"js-base64": {
"version": "2.1.9",
"from": "https://registry.npmjs.org/js-base64/-/js-base64-2.1.9.tgz",
"resolved": "https://registry.npmjs.org/js-base64/-/js-base64-2.1.9.tgz"
}
}
},
"through2": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"dependencies": {
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
}
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
},
"vinyl-sourcemaps-apply": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/vinyl-sourcemaps-apply/-/vinyl-sourcemaps-apply-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/vinyl-sourcemaps-apply/-/vinyl-sourcemaps-apply-0.2.0.tgz",
"dependencies": {
"source-map": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
}
}
}
}
},
"gulp-clang-format": {
"version": "1.0.23",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/gulp-clang-format/-/gulp-clang-format-1.0.23.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/gulp-clang-format/-/gulp-clang-format-1.0.23.tgz",
"dependencies": {
"gulp-diff": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/gulp-diff/-/gulp-diff-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/gulp-diff/-/gulp-diff-1.0.0.tgz",
"dependencies": {
"diff": {
"version": "2.2.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/diff/-/diff-2.2.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/diff/-/diff-2.2.0.tgz"
},
"through2": {
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"dependencies": {
"readable-stream": {
"version": "2.0.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
}
},
"xtend": {
"version": "4.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
},
"cli-color": {
"version": "1.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/cli-color/-/cli-color-1.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/cli-color/-/cli-color-1.1.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
},
"d": {
"version": "0.1.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/d/-/d-0.1.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/d/-/d-0.1.1.tgz"
},
"es5-ext": {
"version": "0.10.8",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/es5-ext/-/es5-ext-0.10.8.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/es5-ext/-/es5-ext-0.10.8.tgz",
"dependencies": {
"es6-symbol": {
"version": "3.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-3.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-3.0.1.tgz"
}
}
},
"es6-iterator": {
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/es6-iterator/-/es6-iterator-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/es6-iterator/-/es6-iterator-2.0.0.tgz",
"dependencies": {
"es6-symbol": {
"version": "3.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-3.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-3.0.1.tgz"
}
}
},
"memoizee": {
"version": "0.3.9",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/memoizee/-/memoizee-0.3.9.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/memoizee/-/memoizee-0.3.9.tgz",
"dependencies": {
"es6-weak-map": {
"version": "0.1.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/es6-weak-map/-/es6-weak-map-0.1.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/es6-weak-map/-/es6-weak-map-0.1.4.tgz",
"dependencies": {
"es6-iterator": {
"version": "0.1.3",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/es6-iterator/-/es6-iterator-0.1.3.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/es6-iterator/-/es6-iterator-0.1.3.tgz"
},
"es6-symbol": {
"version": "2.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-2.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-2.0.1.tgz"
}
}
},
"event-emitter": {
"version": "0.3.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/event-emitter/-/event-emitter-0.3.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/event-emitter/-/event-emitter-0.3.4.tgz"
},
"lru-queue": {
"version": "0.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lru-queue/-/lru-queue-0.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lru-queue/-/lru-queue-0.1.0.tgz"
},
"next-tick": {
"version": "0.2.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/next-tick/-/next-tick-0.2.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/next-tick/-/next-tick-0.2.2.tgz"
}
}
},
"timers-ext": {
"version": "0.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/timers-ext/-/timers-ext-0.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/timers-ext/-/timers-ext-0.1.0.tgz",
"dependencies": {
"next-tick": {
"version": "0.2.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/next-tick/-/next-tick-0.2.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/next-tick/-/next-tick-0.2.2.tgz"
}
}
}
}
},
"event-stream": {
"version": "3.3.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/event-stream/-/event-stream-3.3.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/event-stream/-/event-stream-3.3.2.tgz",
"dependencies": {
"through": {
"version": "2.3.8",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
},
"duplexer": {
"version": "0.1.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/duplexer/-/duplexer-0.1.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/duplexer/-/duplexer-0.1.1.tgz"
},
"from": {
"version": "0.1.3",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/from/-/from-0.1.3.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/from/-/from-0.1.3.tgz"
},
"map-stream": {
"version": "0.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/map-stream/-/map-stream-0.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/map-stream/-/map-stream-0.1.0.tgz"
},
"pause-stream": {
"version": "0.0.11",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pause-stream/-/pause-stream-0.0.11.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pause-stream/-/pause-stream-0.0.11.tgz"
},
"split": {
"version": "0.3.3",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/split/-/split-0.3.3.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/split/-/split-0.3.3.tgz"
},
"stream-combiner": {
"version": "0.0.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/stream-combiner/-/stream-combiner-0.0.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/stream-combiner/-/stream-combiner-0.0.4.tgz"
}
}
}
}
},
"gulp-util": {
"version": "3.0.7",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"array-differ": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
},
"array-uniq": {
"version": "1.0.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
},
"beeper": {
"version": "1.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"chalk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-styles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"escape-string-regexp": {
"version": "1.0.3",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"strip-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"supports-color": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"dateformat": {
"version": "1.0.11",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"meow": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.5.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"map-obj": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"loud-rejection": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.1.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.4.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"object-assign": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.3.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.0.tgz",
"dependencies": {
"is-arrayish": {
"version": "0.2.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz"
}
}
}
}
},
"pify": {
"version": "2.3.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
}
}
},
"trim-newlines": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"fancy-log": {
"version": "1.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulplog": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glogg": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
}
}
},
"has-gulplog": {
"version": "0.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"dependencies": {
"sparkles": {
"version": "1.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
}
}
},
"lodash._reescape": {
"version": "3.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.template": {
"version": "3.6.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"dependencies": {
"lodash._basecopy": {
"version": "3.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._basetostring": {
"version": "3.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._basevalues": {
"version": "3.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
"version": "3.0.9",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
},
"lodash.escape": {
"version": "3.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash.keys": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.1.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._getnative": {
"version": "3.9.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.isarguments": {
"version": "3.0.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.isarray": {
"version": "3.0.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.restparam": {
"version": "3.6.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.templatesettings": {
"version": "3.1.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"multipipe": {
"version": "0.1.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "3.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
},
"replace-ext": {
"version": "0.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"through2": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"isarray": {
"version": "0.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"process-nextick-args": {
"version": "1.0.3",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"string_decoder": {
"version": "0.10.31",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"util-deprecate": {
"version": "1.0.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"xtend": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"vinyl": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.3",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"clone": {
"version": "1.0.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"clone-stats": {
"version": "0.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"pkginfo": {
"version": "0.3.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/pkginfo/-/pkginfo-0.3.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/pkginfo/-/pkginfo-0.3.1.tgz"
},
"stream-combiner2": {
"version": "1.1.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/stream-combiner2/-/stream-combiner2-1.1.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/stream-combiner2/-/stream-combiner2-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"duplexer2": {
"version": "0.1.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.1.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.1.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"readable-stream": {
"version": "2.0.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"stream-equal": {
"version": "0.1.6",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/stream-equal/-/stream-equal-0.1.6.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/stream-equal/-/stream-equal-0.1.6.tgz"
}
}
},
"gulp-concat": {
"version": "2.6.0",
"from": "https://registry.npmjs.org/gulp-concat/-/gulp-concat-2.6.0.tgz",
"resolved": "https://registry.npmjs.org/gulp-concat/-/gulp-concat-2.6.0.tgz",
"dependencies": {
"concat-with-sourcemaps": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/concat-with-sourcemaps/-/concat-with-sourcemaps-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/concat-with-sourcemaps/-/concat-with-sourcemaps-1.0.4.tgz",
"dependencies": {
"source-map": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulp-util": {
"version": "3.0.7",
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"array-differ": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"array-uniq": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"beeper": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.1.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"chalk": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi-styles": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"escape-string-regexp": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"has-ansi": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"supports-color": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"dateformat": {
"version": "1.0.11",
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"get-stdin": {
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"meow": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
}
}
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
}
}
}
}
},
"fancy-log": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz"
},
"gulplog": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"dependencies": {
"glogg": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"dependencies": {
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
}
}
}
}
},
"has-gulplog": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"dependencies": {
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
}
}
},
"lodash._reescape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.template": {
"version": "3.6.2",
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"dependencies": {
"lodash._basecopy": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
},
"lodash._basetostring": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._basevalues": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
"version": "3.0.9",
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
},
"lodash.escape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
},
"lodash.keys": {
"version": "3.1.2",
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"dependencies": {
"lodash._getnative": {
"version": "3.9.1",
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
},
"lodash.isarguments": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
},
"lodash.isarray": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
}
}
},
"lodash.restparam": {
"version": "3.6.1",
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
},
"lodash.templatesettings": {
"version": "3.1.0",
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
}
}
},
"multipipe": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
},
"replace-ext": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
},
"through2": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"dependencies": {
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
}
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
},
"vinyl": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"dependencies": {
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
}
}
}
}
},
"gulp-connect": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/gulp-connect/-/gulp-connect-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/gulp-connect/-/gulp-connect-1.1.1.tgz",
"dependencies": {
"gulp-util": {
"version": "2.2.20",
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-2.2.20.tgz",
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-2.2.20.tgz",
"dependencies": {
"chalk": {
"version": "0.5.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-0.5.1.tgz",
"dependencies": {
"ansi-styles": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-1.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-0.1.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz"
}
}
},
"strip-ansi": {
"version": "0.3.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-0.3.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-0.3.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz"
}
}
},
"supports-color": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-0.2.0.tgz"
}
}
},
"dateformat": {
"version": "1.0.11",
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
},
"meow": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"minimist": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
}
}
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
}
}
}
}
},
"lodash._reinterpolate": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-2.4.1.tgz"
},
"lodash.template": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-2.4.1.tgz",
"dependencies": {
"lodash.defaults": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash.defaults/-/lodash.defaults-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.defaults/-/lodash.defaults-2.4.1.tgz",
"dependencies": {
"lodash._objecttypes": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz"
}
}
},
"lodash.escape": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-2.4.1.tgz",
"dependencies": {
"lodash._escapehtmlchar": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._escapehtmlchar/-/lodash._escapehtmlchar-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._escapehtmlchar/-/lodash._escapehtmlchar-2.4.1.tgz",
"dependencies": {
"lodash._htmlescapes": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._htmlescapes/-/lodash._htmlescapes-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._htmlescapes/-/lodash._htmlescapes-2.4.1.tgz"
}
}
},
"lodash._reunescapedhtml": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._reunescapedhtml/-/lodash._reunescapedhtml-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._reunescapedhtml/-/lodash._reunescapedhtml-2.4.1.tgz",
"dependencies": {
"lodash._htmlescapes": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._htmlescapes/-/lodash._htmlescapes-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._htmlescapes/-/lodash._htmlescapes-2.4.1.tgz"
}
}
}
}
},
"lodash._escapestringchar": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._escapestringchar/-/lodash._escapestringchar-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._escapestringchar/-/lodash._escapestringchar-2.4.1.tgz"
},
"lodash.keys": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-2.4.1.tgz",
"dependencies": {
"lodash._isnative": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._isnative/-/lodash._isnative-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._isnative/-/lodash._isnative-2.4.1.tgz"
},
"lodash.isobject": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash.isobject/-/lodash.isobject-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.isobject/-/lodash.isobject-2.4.1.tgz",
"dependencies": {
"lodash._objecttypes": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz"
}
}
},
"lodash._shimkeys": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._shimkeys/-/lodash._shimkeys-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._shimkeys/-/lodash._shimkeys-2.4.1.tgz",
"dependencies": {
"lodash._objecttypes": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz"
}
}
}
}
},
"lodash.templatesettings": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz"
},
"lodash.values": {
"version": "2.4.1",
"from": "https://registry.npmjs.org/lodash.values/-/lodash.values-2.4.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.values/-/lodash.values-2.4.1.tgz"
}
}
},
"minimist": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/minimist/-/minimist-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.2.0.tgz"
},
"multipipe": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
},
"through2": {
"version": "0.5.1",
"from": "https://registry.npmjs.org/through2/-/through2-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-0.5.1.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"xtend": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/xtend/-/xtend-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-3.0.0.tgz"
}
}
},
"vinyl": {
"version": "0.2.3",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.2.3.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.2.3.tgz",
"dependencies": {
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
}
}
},
"event-stream": {
"version": "3.1.7",
"from": "https://registry.npmjs.org/event-stream/-/event-stream-3.1.7.tgz",
"resolved": "https://registry.npmjs.org/event-stream/-/event-stream-3.1.7.tgz",
"dependencies": {
"through": {
"version": "2.3.8",
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
},
"duplexer": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/duplexer/-/duplexer-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/duplexer/-/duplexer-0.1.1.tgz"
},
"from": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/from/-/from-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/from/-/from-0.1.3.tgz"
},
"map-stream": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/map-stream/-/map-stream-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/map-stream/-/map-stream-0.1.0.tgz"
},
"pause-stream": {
"version": "0.0.11",
"from": "https://registry.npmjs.org/pause-stream/-/pause-stream-0.0.11.tgz",
"resolved": "https://registry.npmjs.org/pause-stream/-/pause-stream-0.0.11.tgz"
},
"split": {
"version": "0.2.10",
"from": "https://registry.npmjs.org/split/-/split-0.2.10.tgz",
"resolved": "https://registry.npmjs.org/split/-/split-0.2.10.tgz"
},
"stream-combiner": {
"version": "0.0.4",
"from": "https://registry.npmjs.org/stream-combiner/-/stream-combiner-0.0.4.tgz",
"resolved": "https://registry.npmjs.org/stream-combiner/-/stream-combiner-0.0.4.tgz"
}
}
},
"connect-livereload": {
"version": "0.3.2",
"from": "https://registry.npmjs.org/connect-livereload/-/connect-livereload-0.3.2.tgz",
"resolved": "https://registry.npmjs.org/connect-livereload/-/connect-livereload-0.3.2.tgz"
},
"open": {
"version": "0.0.4",
"from": "https://registry.npmjs.org/open/-/open-0.0.4.tgz",
"resolved": "https://registry.npmjs.org/open/-/open-0.0.4.tgz"
},
"tiny-lr": {
"version": "0.0.5",
"from": "https://registry.npmjs.org/tiny-lr/-/tiny-lr-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/tiny-lr/-/tiny-lr-0.0.5.tgz",
"dependencies": {
"qs": {
"version": "0.5.6",
"from": "https://registry.npmjs.org/qs/-/qs-0.5.6.tgz",
"resolved": "https://registry.npmjs.org/qs/-/qs-0.5.6.tgz"
},
"faye-websocket": {
"version": "0.4.4",
"from": "https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.4.4.tgz",
"resolved": "https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.4.4.tgz"
},
"noptify": {
"version": "0.0.3",
"from": "https://registry.npmjs.org/noptify/-/noptify-0.0.3.tgz",
"resolved": "https://registry.npmjs.org/noptify/-/noptify-0.0.3.tgz",
"dependencies": {
"nopt": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/nopt/-/nopt-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-2.0.0.tgz",
"dependencies": {
"abbrev": {
"version": "1.0.7",
"from": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz",
"resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz"
}
}
}
}
},
"debug": {
"version": "0.7.4",
"from": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz",
"resolved": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz"
}
}
},
"connect": {
"version": "2.14.5",
"from": "https://registry.npmjs.org/connect/-/connect-2.14.5.tgz",
"resolved": "https://registry.npmjs.org/connect/-/connect-2.14.5.tgz",
"dependencies": {
"basic-auth-connect": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/basic-auth-connect/-/basic-auth-connect-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/basic-auth-connect/-/basic-auth-connect-1.0.0.tgz"
},
"cookie-parser": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/cookie-parser/-/cookie-parser-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/cookie-parser/-/cookie-parser-1.0.1.tgz",
"dependencies": {
"cookie": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/cookie/-/cookie-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/cookie/-/cookie-0.1.0.tgz"
}
}
},
"cookie-signature": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/cookie-signature/-/cookie-signature-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/cookie-signature/-/cookie-signature-1.0.3.tgz"
},
"compression": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/compression/-/compression-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/compression/-/compression-1.0.0.tgz",
"dependencies": {
"bytes": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/bytes/-/bytes-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/bytes/-/bytes-0.2.1.tgz"
},
"negotiator": {
"version": "0.3.0",
"from": "https://registry.npmjs.org/negotiator/-/negotiator-0.3.0.tgz",
"resolved": "https://registry.npmjs.org/negotiator/-/negotiator-0.3.0.tgz"
},
"compressible": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/compressible/-/compressible-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/compressible/-/compressible-1.0.0.tgz"
}
}
},
"connect-timeout": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/connect-timeout/-/connect-timeout-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/connect-timeout/-/connect-timeout-1.0.0.tgz"
},
"csurf": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/csurf/-/csurf-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/csurf/-/csurf-1.1.0.tgz",
"dependencies": {
"uid2": {
"version": "0.0.3",
"from": "https://registry.npmjs.org/uid2/-/uid2-0.0.3.tgz",
"resolved": "https://registry.npmjs.org/uid2/-/uid2-0.0.3.tgz"
},
"scmp": {
"version": "0.0.3",
"from": "https://registry.npmjs.org/scmp/-/scmp-0.0.3.tgz",
"resolved": "https://registry.npmjs.org/scmp/-/scmp-0.0.3.tgz"
}
}
},
"errorhandler": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/errorhandler/-/errorhandler-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/errorhandler/-/errorhandler-1.0.0.tgz"
},
"express-session": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/express-session/-/express-session-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/express-session/-/express-session-1.0.2.tgz",
"dependencies": {
"utils-merge": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/utils-merge/-/utils-merge-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/utils-merge/-/utils-merge-1.0.0.tgz"
},
"cookie": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/cookie/-/cookie-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/cookie/-/cookie-0.1.0.tgz"
},
"uid2": {
"version": "0.0.3",
"from": "https://registry.npmjs.org/uid2/-/uid2-0.0.3.tgz",
"resolved": "https://registry.npmjs.org/uid2/-/uid2-0.0.3.tgz"
},
"buffer-crc32": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.1.tgz"
},
"debug": {
"version": "0.7.4",
"from": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz",
"resolved": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz"
}
}
},
"fresh": {
"version": "0.2.2",
"from": "https://registry.npmjs.org/fresh/-/fresh-0.2.2.tgz",
"resolved": "https://registry.npmjs.org/fresh/-/fresh-0.2.2.tgz"
},
"method-override": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/method-override/-/method-override-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/method-override/-/method-override-1.0.0.tgz",
"dependencies": {
"methods": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/methods/-/methods-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/methods/-/methods-1.1.1.tgz"
}
}
},
"morgan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/morgan/-/morgan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/morgan/-/morgan-1.0.0.tgz",
"dependencies": {
"bytes": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/bytes/-/bytes-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/bytes/-/bytes-0.2.1.tgz"
}
}
},
"qs": {
"version": "0.6.6",
"from": "https://registry.npmjs.org/qs/-/qs-0.6.6.tgz",
"resolved": "https://registry.npmjs.org/qs/-/qs-0.6.6.tgz"
},
"raw-body": {
"version": "1.1.4",
"from": "https://registry.npmjs.org/raw-body/-/raw-body-1.1.4.tgz",
"resolved": "https://registry.npmjs.org/raw-body/-/raw-body-1.1.4.tgz"
},
"response-time": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/response-time/-/response-time-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/response-time/-/response-time-1.0.0.tgz"
},
"setimmediate": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/setimmediate/-/setimmediate-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/setimmediate/-/setimmediate-1.0.1.tgz"
},
"serve-index": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/serve-index/-/serve-index-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/serve-index/-/serve-index-1.0.1.tgz",
"dependencies": {
"batch": {
"version": "0.5.0",
"from": "https://registry.npmjs.org/batch/-/batch-0.5.0.tgz",
"resolved": "https://registry.npmjs.org/batch/-/batch-0.5.0.tgz"
},
"negotiator": {
"version": "0.4.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/negotiator/-/negotiator-0.4.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/negotiator/-/negotiator-0.4.2.tgz"
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"serve-static": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/serve-static/-/serve-static-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/serve-static/-/serve-static-1.1.0.tgz",
"dependencies": {
"parseurl": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/parseurl/-/parseurl-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/parseurl/-/parseurl-1.0.1.tgz"
},
"send": {
"version": "0.3.0",
"from": "https://registry.npmjs.org/send/-/send-0.3.0.tgz",
"resolved": "https://registry.npmjs.org/send/-/send-0.3.0.tgz",
"dependencies": {
"buffer-crc32": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.1.tgz"
},
"debug": {
"version": "0.8.0",
"from": "https://registry.npmjs.org/debug/-/debug-0.8.0.tgz",
"resolved": "https://registry.npmjs.org/debug/-/debug-0.8.0.tgz"
},
"mime": {
"version": "1.2.11",
"from": "https://registry.npmjs.org/mime/-/mime-1.2.11.tgz",
"resolved": "https://registry.npmjs.org/mime/-/mime-1.2.11.tgz"
},
"range-parser": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/range-parser/-/range-parser-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/range-parser/-/range-parser-1.0.3.tgz"
}
}
}
}
},
"static-favicon": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/static-favicon/-/static-favicon-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/static-favicon/-/static-favicon-1.0.2.tgz"
},
"vhost": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/vhost/-/vhost-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/vhost/-/vhost-1.0.0.tgz"
},
"bytes": {
"version": "0.3.0",
"from": "https://registry.npmjs.org/bytes/-/bytes-0.3.0.tgz",
"resolved": "https://registry.npmjs.org/bytes/-/bytes-0.3.0.tgz"
},
"pause": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/pause/-/pause-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/pause/-/pause-0.0.1.tgz"
},
"debug": {
"version": "0.8.1",
"from": "https://registry.npmjs.org/debug/-/debug-0.8.1.tgz",
"resolved": "https://registry.npmjs.org/debug/-/debug-0.8.1.tgz"
},
"multiparty": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/multiparty/-/multiparty-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/multiparty/-/multiparty-2.2.0.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"stream-counter": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/stream-counter/-/stream-counter-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/stream-counter/-/stream-counter-0.2.0.tgz"
}
}
}
}
}
}
},
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"gulp-gzip": {
"version": "1.2.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/gulp-gzip/-/gulp-gzip-1.2.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/gulp-gzip/-/gulp-gzip-1.2.0.tgz",
"dependencies": {
"bytes": {
"version": "0.3.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/bytes/-/bytes-0.3.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/bytes/-/bytes-0.3.0.tgz"
},
"gulp-util": {
"version": "2.2.20",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-2.2.20.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-2.2.20.tgz",
"dependencies": {
"chalk": {
"version": "0.5.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/chalk/-/chalk-0.5.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/chalk/-/chalk-0.5.1.tgz",
"dependencies": {
"ansi-styles": {
"version": "1.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-1.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-1.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "0.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-0.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-0.1.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "0.2.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz"
}
}
},
"strip-ansi": {
"version": "0.3.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-0.3.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-0.3.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "0.2.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz"
}
}
},
"supports-color": {
"version": "0.2.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/supports-color/-/supports-color-0.2.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-0.2.0.tgz"
}
}
},
"dateformat": {
"version": "1.0.11",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
"version": "5.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.1.tgz"
},
"meow": {
"version": "3.5.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
"version": "1.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
"loud-rejection": {
"version": "1.2.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.2.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.2.0.tgz",
"dependencies": {
"signal-exit": {
"version": "2.1.2",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/signal-exit/-/signal-exit-2.1.2.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-2.1.2.tgz"
}
}
},
"minimist": {
"version": "1.2.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.1.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.4",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.4.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.4.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "4.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/find-up/-/find-up-1.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.1.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.1.0.tgz"
},
"pinkie-promise": {
"version": "2.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-2.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-2.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "2.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-2.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-2.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.1.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.3.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.0.tgz",
"dependencies": {
"is-arrayish": {
"version": "0.2.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz"
}
}
}
}
},
"pify": {
"version": "2.3.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "2.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-2.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-2.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "2.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-2.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-2.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/path-type/-/path-type-1.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.1.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "2.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-2.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-2.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "2.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-2.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-2.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
}
}
},
"trim-newlines": {
"version": "1.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
}
}
}
}
},
"lodash._reinterpolate": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-2.4.1.tgz"
},
"lodash.template": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-2.4.1.tgz",
"dependencies": {
"lodash.defaults": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash.defaults/-/lodash.defaults-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash.defaults/-/lodash.defaults-2.4.1.tgz",
"dependencies": {
"lodash._objecttypes": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz"
}
}
},
"lodash.escape": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-2.4.1.tgz",
"dependencies": {
"lodash._escapehtmlchar": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._escapehtmlchar/-/lodash._escapehtmlchar-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._escapehtmlchar/-/lodash._escapehtmlchar-2.4.1.tgz",
"dependencies": {
"lodash._htmlescapes": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._htmlescapes/-/lodash._htmlescapes-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._htmlescapes/-/lodash._htmlescapes-2.4.1.tgz"
}
}
},
"lodash._reunescapedhtml": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._reunescapedhtml/-/lodash._reunescapedhtml-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._reunescapedhtml/-/lodash._reunescapedhtml-2.4.1.tgz",
"dependencies": {
"lodash._htmlescapes": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._htmlescapes/-/lodash._htmlescapes-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._htmlescapes/-/lodash._htmlescapes-2.4.1.tgz"
}
}
}
}
},
"lodash._escapestringchar": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._escapestringchar/-/lodash._escapestringchar-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._escapestringchar/-/lodash._escapestringchar-2.4.1.tgz"
},
"lodash.keys": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-2.4.1.tgz",
"dependencies": {
"lodash._isnative": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._isnative/-/lodash._isnative-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._isnative/-/lodash._isnative-2.4.1.tgz"
},
"lodash.isobject": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash.isobject/-/lodash.isobject-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash.isobject/-/lodash.isobject-2.4.1.tgz",
"dependencies": {
"lodash._objecttypes": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz"
}
}
},
"lodash._shimkeys": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._shimkeys/-/lodash._shimkeys-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._shimkeys/-/lodash._shimkeys-2.4.1.tgz",
"dependencies": {
"lodash._objecttypes": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash._objecttypes/-/lodash._objecttypes-2.4.1.tgz"
}
}
}
}
},
"lodash.templatesettings": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz"
},
"lodash.values": {
"version": "2.4.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/lodash.values/-/lodash.values-2.4.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/lodash.values/-/lodash.values-2.4.1.tgz"
}
}
},
"minimist": {
"version": "0.2.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.2.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.2.0.tgz"
},
"multipipe": {
"version": "0.1.2",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
},
"through2": {
"version": "0.5.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/through2/-/through2-0.5.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/through2/-/through2-0.5.1.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"xtend": {
"version": "3.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/xtend/-/xtend-3.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/xtend/-/xtend-3.0.0.tgz"
}
}
},
"vinyl": {
"version": "0.2.3",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.2.3.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.2.3.tgz",
"dependencies": {
"clone-stats": {
"version": "0.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
}
}
},
"stream-to-array": {
"version": "1.0.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/stream-to-array/-/stream-to-array-1.0.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/stream-to-array/-/stream-to-array-1.0.0.tgz"
},
"through2": {
"version": "0.4.2",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/through2/-/through2-0.4.2.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/through2/-/through2-0.4.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"xtend": {
"version": "2.1.2",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/xtend/-/xtend-2.1.2.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/xtend/-/xtend-2.1.2.tgz",
"dependencies": {
"object-keys": {
"version": "0.4.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"from": "https://registry.npmjs.org/object-keys/-/object-keys-0.4.0.tgz",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-0.4.0.tgz"
}
}
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulp-insert": {
"version": "0.5.0",
"from": "https://registry.npmjs.org/gulp-insert/-/gulp-insert-0.5.0.tgz",
"resolved": "https://registry.npmjs.org/gulp-insert/-/gulp-insert-0.5.0.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"streamqueue": {
"version": "0.0.6",
"from": "https://registry.npmjs.org/streamqueue/-/streamqueue-0.0.6.tgz",
"resolved": "https://registry.npmjs.org/streamqueue/-/streamqueue-0.0.6.tgz"
}
}
},
"gulp-load-plugins": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/gulp-load-plugins/-/gulp-load-plugins-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/gulp-load-plugins/-/gulp-load-plugins-1.0.0.tgz",
"dependencies": {
"findup-sync": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.2.1.tgz",
"dependencies": {
"glob": {
"version": "4.3.5",
"from": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
}
}
},
"multimatch": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/multimatch/-/multimatch-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/multimatch/-/multimatch-2.0.0.tgz",
"dependencies": {
"array-differ": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
},
"array-union": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/array-union/-/array-union-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/array-union/-/array-union-1.0.1.tgz",
"dependencies": {
"array-uniq": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
}
}
}
}
},
"resolve": {
"version": "1.1.6",
"from": "https://registry.npmjs.org/resolve/-/resolve-1.1.6.tgz",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.1.6.tgz"
}
}
},
"gulp-rename": {
"version": "1.2.2",
"from": "https://registry.npmjs.org/gulp-rename/-/gulp-rename-1.2.2.tgz",
"resolved": "https://registry.npmjs.org/gulp-rename/-/gulp-rename-1.2.2.tgz"
},
"gulp-replace": {
"version": "0.5.4",
"from": "https://registry.npmjs.org/gulp-replace/-/gulp-replace-0.5.4.tgz",
"resolved": "https://registry.npmjs.org/gulp-replace/-/gulp-replace-0.5.4.tgz",
"dependencies": {
"istextorbinary": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/istextorbinary/-/istextorbinary-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/istextorbinary/-/istextorbinary-1.0.2.tgz",
"dependencies": {
"textextensions": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/textextensions/-/textextensions-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/textextensions/-/textextensions-1.0.1.tgz"
},
"binaryextensions": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/binaryextensions/-/binaryextensions-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/binaryextensions/-/binaryextensions-1.0.0.tgz"
}
}
},
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
}
},
"replacestream": {
"version": "4.0.0",
"from": "https://registry.npmjs.org/replacestream/-/replacestream-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/replacestream/-/replacestream-4.0.0.tgz",
"dependencies": {
"escape-string-regexp": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"object-assign": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
}
}
}
}
},
"gulp-sass": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/gulp-sass/-/gulp-sass-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/gulp-sass/-/gulp-sass-2.1.0.tgz",
"dependencies": {
"gulp-util": {
"version": "3.0.7",
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"dependencies": {
"array-differ": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
},
"array-uniq": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
},
"beeper": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
},
"chalk": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"dependencies": {
"ansi-styles": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"supports-color": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
}
}
},
"dateformat": {
"version": "1.0.11",
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
},
"meow": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
}
}
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
}
}
}
}
},
"fancy-log": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz"
},
"gulplog": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"dependencies": {
"glogg": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"dependencies": {
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
}
}
}
}
},
"has-gulplog": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"dependencies": {
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
}
}
},
"lodash._reescape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.template": {
"version": "3.6.2",
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"dependencies": {
"lodash._basecopy": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
},
"lodash._basetostring": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._basevalues": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
"version": "3.0.9",
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
},
"lodash.escape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
},
"lodash.keys": {
"version": "3.1.2",
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"dependencies": {
"lodash._getnative": {
"version": "3.9.1",
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
},
"lodash.isarguments": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
},
"lodash.isarray": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
}
}
},
"lodash.restparam": {
"version": "3.6.1",
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
},
"lodash.templatesettings": {
"version": "3.1.0",
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
}
}
},
"multipipe": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
},
"replace-ext": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
},
"vinyl": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"dependencies": {
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
}
}
},
"node-sass": {
"version": "3.4.1",
"from": "https://registry.npmjs.org/node-sass/-/node-sass-3.4.1.tgz",
"resolved": "https://registry.npmjs.org/node-sass/-/node-sass-3.4.1.tgz",
"dependencies": {
"async-foreach": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/async-foreach/-/async-foreach-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/async-foreach/-/async-foreach-0.1.3.tgz"
},
"chalk": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"dependencies": {
"ansi-styles": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"supports-color": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
}
}
},
"cross-spawn": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"cross-spawn-async": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/cross-spawn-async/-/cross-spawn-async-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/cross-spawn-async/-/cross-spawn-async-2.0.0.tgz",
"dependencies": {
"lru-cache": {
"version": "2.7.0",
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz"
}
}
},
"spawn-sync": {
"version": "1.0.14",
"from": "https://registry.npmjs.org/spawn-sync/-/spawn-sync-1.0.14.tgz",
"resolved": "https://registry.npmjs.org/spawn-sync/-/spawn-sync-1.0.14.tgz",
"dependencies": {
"concat-stream": {
"version": "1.5.1",
"from": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.5.1.tgz",
"resolved": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.5.1.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"typedarray": {
"version": "0.0.6",
"from": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz",
"resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz"
},
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
}
}
}
},
"os-shim": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/os-shim/-/os-shim-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/os-shim/-/os-shim-0.1.3.tgz"
}
}
}
}
},
"gaze": {
"version": "0.5.2",
"from": "https://registry.npmjs.org/gaze/-/gaze-0.5.2.tgz",
"resolved": "https://registry.npmjs.org/gaze/-/gaze-0.5.2.tgz",
"dependencies": {
"globule": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/globule/-/globule-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/globule/-/globule-0.1.0.tgz",
"dependencies": {
"lodash": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz"
},
"glob": {
"version": "3.1.21",
"from": "https://registry.npmjs.org/glob/-/glob-3.1.21.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-3.1.21.tgz",
"dependencies": {
"graceful-fs": {
"version": "1.2.3",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-1.2.3.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-1.2.3.tgz"
},
"inherits": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/inherits/-/inherits-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-1.0.2.tgz"
}
}
},
"minimatch": {
"version": "0.2.14",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-0.2.14.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.2.14.tgz",
"dependencies": {
"lru-cache": {
"version": "2.7.0",
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz"
},
"sigmund": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz"
}
}
}
}
}
}
},
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
},
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
},
"meow": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"mkdirp": {
"version": "0.5.1",
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"nan": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/nan/-/nan-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/nan/-/nan-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"npmconf": {
"version": "2.1.2",
"from": "https://registry.npmjs.org/npmconf/-/npmconf-2.1.2.tgz",
"resolved": "https://registry.npmjs.org/npmconf/-/npmconf-2.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"config-chain": {
"version": "1.1.9",
"from": "https://registry.npmjs.org/config-chain/-/config-chain-1.1.9.tgz",
"resolved": "https://registry.npmjs.org/config-chain/-/config-chain-1.1.9.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"proto-list": {
"version": "1.2.4",
"from": "https://registry.npmjs.org/proto-list/-/proto-list-1.2.4.tgz",
"resolved": "https://registry.npmjs.org/proto-list/-/proto-list-1.2.4.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"ini": {
"version": "1.3.4",
"from": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz",
"resolved": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz"
},
"nopt": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/nopt/-/nopt-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-3.0.4.tgz",
"dependencies": {
"abbrev": {
"version": "1.0.7",
"from": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz",
"resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz"
}
}
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"osenv": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"dependencies": {
"os-homedir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"os-tmpdir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz"
}
}
},
"uid-number": {
"version": "0.0.5",
"from": "https://registry.npmjs.org/uid-number/-/uid-number-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/uid-number/-/uid-number-0.0.5.tgz"
}
}
},
"node-gyp": {
"version": "3.0.3",
"from": "https://registry.npmjs.org/node-gyp/-/node-gyp-3.0.3.tgz",
"resolved": "https://registry.npmjs.org/node-gyp/-/node-gyp-3.0.3.tgz",
"dependencies": {
"fstream": {
"version": "1.0.8",
"from": "https://registry.npmjs.org/fstream/-/fstream-1.0.8.tgz",
"resolved": "https://registry.npmjs.org/fstream/-/fstream-1.0.8.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"glob": {
"version": "4.5.3",
"from": "https://registry.npmjs.org/glob/-/glob-4.5.3.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-4.5.3.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"minimatch": {
"version": "2.0.10",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.10.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.10.tgz",
"dependencies": {
"brace-expansion": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"dependencies": {
"balanced-match": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz"
},
"concat-map": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
}
}
}
}
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"minimatch": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"lru-cache": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.7.0",
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"sigmund": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.1",
"from": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"nopt": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/nopt/-/nopt-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-3.0.4.tgz",
"dependencies": {
"abbrev": {
"version": "1.0.7",
"from": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz",
"resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.0.7.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"npmlog": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/npmlog/-/npmlog-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/npmlog/-/npmlog-1.2.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi": {
"version": "0.3.0",
"from": "https://registry.npmjs.org/ansi/-/ansi-0.3.0.tgz",
"resolved": "https://registry.npmjs.org/ansi/-/ansi-0.3.0.tgz"
},
"are-we-there-yet": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/are-we-there-yet/-/are-we-there-yet-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/are-we-there-yet/-/are-we-there-yet-1.0.4.tgz",
"dependencies": {
"delegates": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/delegates/-/delegates-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/delegates/-/delegates-0.1.0.tgz"
},
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
},
"gauge": {
"version": "1.2.2",
"from": "https://registry.npmjs.org/gauge/-/gauge-1.2.2.tgz",
"resolved": "https://registry.npmjs.org/gauge/-/gauge-1.2.2.tgz",
"dependencies": {
"has-unicode": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/has-unicode/-/has-unicode-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/has-unicode/-/has-unicode-1.0.1.tgz"
},
"lodash.pad": {
"version": "3.1.1",
"from": "https://registry.npmjs.org/lodash.pad/-/lodash.pad-3.1.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.pad/-/lodash.pad-3.1.1.tgz",
"dependencies": {
"lodash._basetostring": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._createpadding": {
"version": "3.6.1",
"from": "https://registry.npmjs.org/lodash._createpadding/-/lodash._createpadding-3.6.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._createpadding/-/lodash._createpadding-3.6.1.tgz",
"dependencies": {
"lodash.repeat": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash.repeat/-/lodash.repeat-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.repeat/-/lodash.repeat-3.0.1.tgz"
}
}
}
}
},
"lodash.padleft": {
"version": "3.1.1",
"from": "https://registry.npmjs.org/lodash.padleft/-/lodash.padleft-3.1.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.padleft/-/lodash.padleft-3.1.1.tgz",
"dependencies": {
"lodash._basetostring": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._createpadding": {
"version": "3.6.1",
"from": "https://registry.npmjs.org/lodash._createpadding/-/lodash._createpadding-3.6.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._createpadding/-/lodash._createpadding-3.6.1.tgz",
"dependencies": {
"lodash.repeat": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash.repeat/-/lodash.repeat-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.repeat/-/lodash.repeat-3.0.1.tgz"
}
}
}
}
},
"lodash.padright": {
"version": "3.1.1",
"from": "https://registry.npmjs.org/lodash.padright/-/lodash.padright-3.1.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.padright/-/lodash.padright-3.1.1.tgz",
"dependencies": {
"lodash._basetostring": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._createpadding": {
"version": "3.6.1",
"from": "https://registry.npmjs.org/lodash._createpadding/-/lodash._createpadding-3.6.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._createpadding/-/lodash._createpadding-3.6.1.tgz",
"dependencies": {
"lodash.repeat": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash.repeat/-/lodash.repeat-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.repeat/-/lodash.repeat-3.0.1.tgz"
}
}
}
}
}
}
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"osenv": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"os-homedir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz"
},
"os-tmpdir": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"path-array": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-array/-/path-array-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-array/-/path-array-1.0.0.tgz",
"dependencies": {
"array-index": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/array-index/-/array-index-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/array-index/-/array-index-0.1.1.tgz",
"dependencies": {
"debug": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
"dependencies": {
"ms": {
"version": "0.7.1",
"from": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz",
"resolved": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"
}
}
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"rimraf": {
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"minimatch": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.0.tgz",
"dependencies": {
"brace-expansion": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"dependencies": {
"balanced-match": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz"
},
"concat-map": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
}
}
}
}
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"tar": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/tar/-/tar-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/tar/-/tar-1.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"block-stream": {
"version": "0.0.8",
"from": "https://registry.npmjs.org/block-stream/-/block-stream-0.0.8.tgz",
"resolved": "https://registry.npmjs.org/block-stream/-/block-stream-0.0.8.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"request": {
"version": "2.65.0",
"from": "https://registry.npmjs.org/request/-/request-2.65.0.tgz",
"resolved": "https://registry.npmjs.org/request/-/request-2.65.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"bl": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
build(npm): resolve shrinkwrap conflicts after rebase
2015-09-26 00:42:41 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"isarray": {
"version": "0.0.1",
build(npm): resolve shrinkwrap conflicts after rebase
2015-09-26 00:42:41 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"string_decoder": {
"version": "0.10.31",
build(npm): resolve shrinkwrap conflicts after rebase
2015-09-26 00:42:41 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"caseless": {
"version": "0.11.0",
"from": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz",
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz"
},
"extend": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz"
},
"forever-agent": {
"version": "0.6.1",
"from": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz",
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz"
},
"form-data": {
"version": "1.0.0-rc3",
"from": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
"resolved": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"async": {
"version": "1.5.0",
"from": "https://registry.npmjs.org/async/-/async-1.5.0.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-1.5.0.tgz"
}
}
},
"json-stringify-safe": {
"version": "5.0.1",
"from": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
},
"mime-types": {
"version": "2.1.7",
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
"dependencies": {
"mime-db": {
"version": "1.19.0",
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz"
}
}
},
"qs": {
"version": "5.2.0",
"from": "https://registry.npmjs.org/qs/-/qs-5.2.0.tgz",
"resolved": "https://registry.npmjs.org/qs/-/qs-5.2.0.tgz"
},
"tunnel-agent": {
"version": "0.4.1",
"from": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz",
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz"
},
"tough-cookie": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz"
},
"http-signature": {
"version": "0.11.0",
"from": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
"dependencies": {
"assert-plus": {
"version": "0.1.5",
"from": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz",
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"asn1": {
"version": "0.1.11",
"from": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz",
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ctype": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz"
}
}
},
"oauth-sign": {
"version": "0.8.0",
"from": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz",
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz"
},
"hawk": {
"version": "3.1.0",
"from": "https://registry.npmjs.org/hawk/-/hawk-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/hawk/-/hawk-3.1.0.tgz",
"dependencies": {
"hoek": {
"version": "2.16.3",
"from": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz",
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"boom": {
"version": "2.10.1",
"from": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz",
"resolved": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"cryptiles": {
"version": "2.0.5",
"from": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz",
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz"
},
"sntp": {
"version": "1.0.9",
"from": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz",
"resolved": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"aws-sign2": {
"version": "0.6.0",
"from": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.6.0.tgz",
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.6.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"stringstream": {
"version": "0.0.5",
"from": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"combined-stream": {
"version": "1.0.5",
"from": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"delayed-stream": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"isstream": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"har-validator": {
"version": "2.0.2",
"from": "https://registry.npmjs.org/har-validator/-/har-validator-2.0.2.tgz",
"resolved": "https://registry.npmjs.org/har-validator/-/har-validator-2.0.2.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"commander": {
"version": "2.9.0",
"from": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"graceful-readlink": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"is-my-json-valid": {
"version": "2.12.2",
"from": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
"resolved": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"generate-function": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"generate-object-property": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-property": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"jsonpointer": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz"
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sass-graph": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/sass-graph/-/sass-graph-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/sass-graph/-/sass-graph-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash": {
"version": "3.10.1",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
},
"yargs": {
"version": "3.29.0",
"from": "https://registry.npmjs.org/yargs/-/yargs-3.29.0.tgz",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-3.29.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"cliui": {
"version": "3.0.3",
"from": "https://registry.npmjs.org/cliui/-/cliui-3.0.3.tgz",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-3.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"string-width": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/string-width/-/string-width-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-1.0.1.tgz",
"dependencies": {
"code-point-at": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/code-point-at/-/code-point-at-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/code-point-at/-/code-point-at-1.0.0.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
},
"is-fullwidth-code-point": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
},
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"wrap-ansi": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"decamelize": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/decamelize/-/decamelize-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/decamelize/-/decamelize-1.1.1.tgz"
},
"os-locale": {
"version": "1.4.0",
"from": "https://registry.npmjs.org/os-locale/-/os-locale-1.4.0.tgz",
"resolved": "https://registry.npmjs.org/os-locale/-/os-locale-1.4.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lcid": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/lcid/-/lcid-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/lcid/-/lcid-1.0.0.tgz",
"dependencies": {
"invert-kv": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/invert-kv/-/invert-kv-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/invert-kv/-/invert-kv-1.0.0.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"window-size": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/window-size/-/window-size-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/window-size/-/window-size-0.1.2.tgz"
},
"y18n": {
"version": "3.2.0",
"from": "https://registry.npmjs.org/y18n/-/y18n-3.2.0.tgz",
"resolved": "https://registry.npmjs.org/y18n/-/y18n-3.2.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
}
}
},
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"through2": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"dependencies": {
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
"inherits": {
"version": "2.0.1",
build(npm): resolve shrinkwrap conflicts after rebase
2015-09-26 00:42:41 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
},
"vinyl-sourcemaps-apply": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/vinyl-sourcemaps-apply/-/vinyl-sourcemaps-apply-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/vinyl-sourcemaps-apply/-/vinyl-sourcemaps-apply-0.2.0.tgz",
"dependencies": {
"source-map": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
}
}
}
}
},
"gulp-shell": {
"version": "0.5.1",
"from": "https://registry.npmjs.org/gulp-shell/-/gulp-shell-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/gulp-shell/-/gulp-shell-0.5.1.tgz",
"dependencies": {
"async": {
"version": "1.5.0",
"from": "https://registry.npmjs.org/async/-/async-1.5.0.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-1.5.0.tgz"
},
"gulp-util": {
"version": "3.0.7",
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"dependencies": {
"array-differ": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"array-uniq": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"beeper": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
},
"chalk": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi-styles": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"escape-string-regexp": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"has-ansi": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"supports-color": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"dateformat": {
"version": "1.0.11",
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"get-stdin": {
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"meow": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"camelcase-keys": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"find-up": {
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"fancy-log": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz"
},
"gulplog": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glogg": {
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
}
}
},
"has-gulplog": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"dependencies": {
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
}
}
},
"lodash._reescape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.template": {
"version": "3.6.2",
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"dependencies": {
"lodash._basecopy": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._basetostring": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._basevalues": {
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"version": "3.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._isiterateecall": {
"version": "3.0.9",
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.escape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.keys": {
"version": "3.1.2",
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._getnative": {
"version": "3.9.1",
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.isarguments": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
},
"lodash.isarray": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.restparam": {
"version": "3.6.1",
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.templatesettings": {
"version": "3.1.0",
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
}
}
},
"multipipe": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"core-util-is": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
},
"replace-ext": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
},
"vinyl": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
}
}
},
"lodash": {
"version": "3.10.1",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
},
"through2": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"dependencies": {
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
}
}
},
"gulp-sourcemaps": {
"version": "1.6.0",
"from": "https://registry.npmjs.org/gulp-sourcemaps/-/gulp-sourcemaps-1.6.0.tgz",
"resolved": "https://registry.npmjs.org/gulp-sourcemaps/-/gulp-sourcemaps-1.6.0.tgz",
"dependencies": {
"convert-source-map": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.1.1.tgz"
},
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"through2": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
},
"vinyl": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-1.1.0.tgz",
"dependencies": {
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
},
"replace-ext": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"gulp-tslint": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.5.0",
"from": "https://registry.npmjs.org/gulp-tslint/-/gulp-tslint-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/gulp-tslint/-/gulp-tslint-3.5.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"dependencies": {
"gulp-util": {
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"version": "3.0.7",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"dependencies": {
"array-differ": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
},
"array-uniq": {
"version": "1.0.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
},
"beeper": {
"version": "1.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
},
"chalk": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.1.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"dependencies": {
"ansi-styles": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
},
"escape-string-regexp": {
"version": "1.0.3",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"dependencies": {
"ansi-regex": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
}
}
},
"supports-color": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
}
}
},
"dateformat": {
"version": "1.0.11",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "5.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
},
"meow": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.2.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
},
"map-obj": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
},
"loud-rejection": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "4.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
}
}
},
"trim-newlines": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
}
}
}
}
},
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"fancy-log": {
"version": "1.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz"
},
"gulplog": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"dependencies": {
"glogg": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"dependencies": {
"sparkles": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
}
}
}
}
},
"has-gulplog": {
"version": "0.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"dependencies": {
"sparkles": {
"version": "1.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
}
}
},
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"lodash._reescape": {
"version": "3.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.template": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "3.6.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"dependencies": {
"lodash._basecopy": {
"version": "3.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
},
"lodash._basetostring": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "3.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
},
"lodash._basevalues": {
"version": "3.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
"version": "3.0.9",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
},
"lodash.escape": {
"version": "3.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
},
"lodash.keys": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "3.1.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"dependencies": {
"lodash._getnative": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "3.9.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
},
"lodash.isarguments": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "3.0.4",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
},
"lodash.isarray": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "3.0.4",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
}
}
},
"lodash.restparam": {
"version": "3.6.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
},
"lodash.templatesettings": {
"version": "3.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
}
}
},
"multipipe": {
"version": "0.1.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "3.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
},
"replace-ext": {
"version": "0.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
},
"through2": {
"version": "2.0.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"dependencies": {
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.0.3",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
},
"string_decoder": {
"version": "0.10.31",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"version": "1.0.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
}
}
},
"vinyl": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "0.5.3",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"dependencies": {
"clone": {
"version": "1.0.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
"clone-stats": {
"version": "0.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
}
}
},
"map-stream": {
"version": "0.1.0",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/map-stream/-/map-stream-0.1.0.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/map-stream/-/map-stream-0.1.0.tgz"
},
"rcloader": {
"version": "0.1.4",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/rcloader/-/rcloader-0.1.4.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/rcloader/-/rcloader-0.1.4.tgz",
"dependencies": {
"lodash": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "3.10.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
},
"rcfinder": {
"version": "0.1.8",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/rcfinder/-/rcfinder-0.1.8.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/rcfinder/-/rcfinder-0.1.8.tgz",
"dependencies": {
"lodash": {
"version": "2.4.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz",
feat(build): add tslint to the build. The first enabled rule enforces return types declared on non-private (underscore-prefix) methods that return something.
2015-06-24 18:36:16 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz"
}
}
}
}
},
"through": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.3.8",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
},
"tslint": {
"version": "2.5.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/tslint/-/tslint-2.5.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/tslint/-/tslint-2.5.1.tgz",
"dependencies": {
"findup-sync": {
"version": "0.2.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.2.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.2.1.tgz",
"dependencies": {
"glob": {
"version": "4.3.5",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
}
}
},
"optimist": {
"version": "0.6.1",
"from": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
"dependencies": {
"wordwrap": {
"version": "0.0.3",
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
},
"minimist": {
"version": "0.0.10",
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz"
}
}
},
"underscore.string": {
"version": "3.1.1",
"from": "https://registry.npmjs.org/underscore.string/-/underscore.string-3.1.1.tgz",
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-3.1.1.tgz"
}
}
}
}
},
"gulp-typescript": {
"version": "2.9.2",
"from": "https://registry.npmjs.org/gulp-typescript/-/gulp-typescript-2.9.2.tgz",
"resolved": "https://registry.npmjs.org/gulp-typescript/-/gulp-typescript-2.9.2.tgz",
"dependencies": {
"gulp-util": {
"version": "3.0.7",
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"dependencies": {
"array-differ": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
},
"array-uniq": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
},
"beeper": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
},
"chalk": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"dependencies": {
"ansi-styles": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"supports-color": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
}
}
},
"dateformat": {
"version": "1.0.11",
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
},
"meow": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"fancy-log": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "1.1.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulplog": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glogg": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"has-gulplog": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"lodash._reescape": {
"version": "3.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.template": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "3.6.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"lodash._basecopy": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"version": "3.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash._basetostring": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "3.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash._basevalues": {
"version": "3.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "3.0.9",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash.escape": {
"version": "3.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
},
"lodash.keys": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "3.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"lodash._getnative": {
"version": "3.9.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"lodash.isarguments": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "3.0.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash.isarray": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "3.0.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"lodash.restparam": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"version": "3.6.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash.templatesettings": {
"version": "3.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
}
}
},
"multipipe": {
"version": "0.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
},
"object-assign": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "3.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"replace-ext": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
},
"vinyl": {
"version": "0.5.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"dependencies": {
"clone": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
"clone-stats": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"source-map": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.3",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
},
"through2": {
"version": "2.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
},
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"vinyl-fs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.1",
"from": "https://registry.npmjs.org/vinyl-fs/-/vinyl-fs-2.1.1.tgz",
"resolved": "https://registry.npmjs.org/vinyl-fs/-/vinyl-fs-2.1.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"dependencies": {
"duplexify": {
"version": "3.4.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/duplexify/-/duplexify-3.4.2.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/duplexify/-/duplexify-3.4.2.tgz",
"dependencies": {
"end-of-stream": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.0.0.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.0.0.tgz",
"dependencies": {
"once": {
"version": "1.3.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
}
}
}
},
"glob-stream": {
"version": "5.0.0",
"from": "https://registry.npmjs.org/glob-stream/-/glob-stream-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/glob-stream/-/glob-stream-5.0.0.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
},
"ordered-read-streams": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/ordered-read-streams/-/ordered-read-streams-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/ordered-read-streams/-/ordered-read-streams-0.2.0.tgz",
"dependencies": {
"isstream": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
},
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
},
"glob2base": {
"version": "0.0.12",
"from": "https://registry.npmjs.org/glob2base/-/glob2base-0.0.12.tgz",
"resolved": "https://registry.npmjs.org/glob2base/-/glob2base-0.0.12.tgz",
"dependencies": {
"find-index": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/find-index/-/find-index-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/find-index/-/find-index-0.1.1.tgz"
}
}
},
"unique-stream": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/unique-stream/-/unique-stream-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/unique-stream/-/unique-stream-2.2.0.tgz"
},
"through2": {
"version": "0.6.5",
"from": "https://registry.npmjs.org/through2/-/through2-0.6.5.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-0.6.5.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
}
}
},
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"is-valid-glob": {
"version": "0.3.0",
"from": "https://registry.npmjs.org/is-valid-glob/-/is-valid-glob-0.3.0.tgz",
"resolved": "https://registry.npmjs.org/is-valid-glob/-/is-valid-glob-0.3.0.tgz"
},
"merge-stream": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/merge-stream/-/merge-stream-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/merge-stream/-/merge-stream-1.0.0.tgz",
"dependencies": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
}
}
}
}
},
"mkdirp": {
"version": "0.5.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
},
"object-assign": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
},
"strip-bom": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
},
"strip-bom-stream": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/strip-bom-stream/-/strip-bom-stream-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom-stream/-/strip-bom-stream-1.0.0.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"dependencies": {
"first-chunk-stream": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/first-chunk-stream/-/first-chunk-stream-1.0.0.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"resolved": "https://registry.npmjs.org/first-chunk-stream/-/first-chunk-stream-1.0.0.tgz"
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"through2-filter": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/through2-filter/-/through2-filter-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/through2-filter/-/through2-filter-2.0.0.tgz",
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
},
"vinyl": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-1.1.0.tgz",
"dependencies": {
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
},
"replace-ext": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"gulp-uglify": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.4.2",
"from": "https://registry.npmjs.org/gulp-uglify/-/gulp-uglify-1.4.2.tgz",
"resolved": "https://registry.npmjs.org/gulp-uglify/-/gulp-uglify-1.4.2.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"dependencies": {
"deap": {
"version": "1.0.0",
chore(package.json): bump dgeni-packages version
2015-06-11 17:28:19 -04:00
"from": "https://registry.npmjs.org/deap/-/deap-1.0.0.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"resolved": "https://registry.npmjs.org/deap/-/deap-1.0.0.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"fancy-log": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
"dependencies": {
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"chalk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"dependencies": {
"ansi-styles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
},
"escape-string-regexp": {
"version": "1.0.3",
chore(package.json): bump dgeni-packages version
2015-06-11 17:28:19 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
}
}
},
"supports-color": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
}
}
},
"dateformat": {
"version": "1.0.11",
chore(package.json): bump dgeni-packages version
2015-06-11 17:28:19 -04:00
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
},
"meow": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
chore(package.json): bump dgeni-packages version
2015-06-11 17:28:19 -04:00
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
},
"map-obj": {
"version": "1.0.1",
chore(package.json): bump dgeni-packages version
2015-06-11 17:28:19 -04:00
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
}
}
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulp-util": {
"version": "3.0.7",
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"array-differ": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"array-uniq": {
fix(build): Minify files for angular2.min.js bundle Uglify files related to angular2.min.js bundle in one task. Include reflect.js in the bundle, which was previously missing. Minify reflect.js, zone.js, and angular2.min.js using uglify.
2015-06-08 20:15:40 -04:00
"version": "1.0.2",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"beeper": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"chalk": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-styles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"escape-string-regexp": {
"version": "1.0.3",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"strip-ansi": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ansi-regex": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"supports-color": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
}
}
},
"dateformat": {
"version": "1.0.11",
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"dependencies": {
"get-stdin": {
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
},
"meow": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"dependencies": {
"camelcase-keys": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
}
}
},
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"dependencies": {
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
}
}
},
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"dependencies": {
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
}
}
},
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulplog": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glogg": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"has-gulplog": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"dependencies": {
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
}
}
},
"lodash._reescape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"lodash._reinterpolate": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash.template": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.6.2",
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._basecopy": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._basetostring": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._basevalues": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
"version": "3.0.9",
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
},
"lodash.escape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"lodash.keys": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.1.2",
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._getnative": {
"version": "3.9.1",
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.isarguments": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.isarray": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.restparam": {
"version": "3.6.1",
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash.templatesettings": {
"version": "3.1.0",
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"multipipe": {
"version": "0.1.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
},
"replace-ext": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"vinyl": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.3",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"clone-stats": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"isobject": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/isobject/-/isobject-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/isobject/-/isobject-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"through2": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.0",
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"xtend": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"uglify-js": {
"version": "2.5.0",
"from": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.5.0.tgz",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.5.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"async": {
"version": "0.2.10",
"from": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"source-map": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"uglify-to-browserify": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz"
},
"yargs": {
"version": "3.5.4",
"from": "https://registry.npmjs.org/yargs/-/yargs-3.5.4.tgz",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-3.5.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"decamelize": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/decamelize/-/decamelize-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/decamelize/-/decamelize-1.1.1.tgz"
},
"window-size": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/window-size/-/window-size-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/window-size/-/window-size-0.1.0.tgz"
},
"wordwrap": {
"version": "0.0.2",
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz",
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"uglify-save-license": {
"version": "0.4.1",
"from": "https://registry.npmjs.org/uglify-save-license/-/uglify-save-license-0.4.1.tgz",
"resolved": "https://registry.npmjs.org/uglify-save-license/-/uglify-save-license-0.4.1.tgz"
},
"vinyl-sourcemaps-apply": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/vinyl-sourcemaps-apply/-/vinyl-sourcemaps-apply-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/vinyl-sourcemaps-apply/-/vinyl-sourcemaps-apply-0.2.0.tgz",
"dependencies": {
"source-map": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"hash-files": {
"version": "1.0.0",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"from": "https://registry.npmjs.org/hash-files/-/hash-files-1.0.0.tgz",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"resolved": "https://registry.npmjs.org/hash-files/-/hash-files-1.0.0.tgz",
"dependencies": {
"glob": {
"version": "3.2.11",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"minimatch": {
"version": "0.3.0",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"from": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz",
"dependencies": {
"lru-cache": {
"version": "2.7.0",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz"
},
"sigmund": {
"version": "1.0.1",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"from": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz"
}
}
}
}
},
"read-files": {
"version": "0.1.0",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"from": "https://registry.npmjs.org/read-files/-/read-files-0.1.0.tgz",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"resolved": "https://registry.npmjs.org/read-files/-/read-files-0.1.0.tgz"
},
"underscore": {
"version": "1.8.3",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"from": "https://registry.npmjs.org/underscore/-/underscore-1.8.3.tgz",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"resolved": "https://registry.npmjs.org/underscore/-/underscore-1.8.3.tgz"
},
"async": {
"version": "0.9.2",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.9.2.tgz",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
}
}
},
chore(testing): update karma-jasmine and jasmine Jasmine to jasmine-core 2.3.4. Update tools tests using minijasminenode to directly use jasmine. See #1860
2015-05-20 19:07:47 -04:00
"jasmine": {
"version": "2.3.1",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"from": "https://registry.npmjs.org/jasmine/-/jasmine-2.3.1.tgz",
chore(testing): update karma-jasmine and jasmine Jasmine to jasmine-core 2.3.4. Update tools tests using minijasminenode to directly use jasmine. See #1860
2015-05-20 19:07:47 -04:00
"resolved": "https://registry.npmjs.org/jasmine/-/jasmine-2.3.1.tgz",
"dependencies": {
"exit": {
"version": "0.1.2",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"from": "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz",
chore(testing): update karma-jasmine and jasmine Jasmine to jasmine-core 2.3.4. Update tools tests using minijasminenode to directly use jasmine. See #1860
2015-05-20 19:07:47 -04:00
"resolved": "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz"
},
"glob": {
"version": "3.2.11",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz",
chore(testing): update karma-jasmine and jasmine Jasmine to jasmine-core 2.3.4. Update tools tests using minijasminenode to directly use jasmine. See #1860
2015-05-20 19:07:47 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(testing): update karma-jasmine and jasmine Jasmine to jasmine-core 2.3.4. Update tools tests using minijasminenode to directly use jasmine. See #1860
2015-05-20 19:07:47 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"minimatch": {
"version": "0.3.0",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"from": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz",
chore(testing): update karma-jasmine and jasmine Jasmine to jasmine-core 2.3.4. Update tools tests using minijasminenode to directly use jasmine. See #1860
2015-05-20 19:07:47 -04:00
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz",
"dependencies": {
"lru-cache": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.7.0",
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz"
chore(testing): update karma-jasmine and jasmine Jasmine to jasmine-core 2.3.4. Update tools tests using minijasminenode to directly use jasmine. See #1860
2015-05-20 19:07:47 -04:00
},
"sigmund": {
"version": "1.0.1",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"from": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz",
chore(testing): update karma-jasmine and jasmine Jasmine to jasmine-core 2.3.4. Update tools tests using minijasminenode to directly use jasmine. See #1860
2015-05-20 19:07:47 -04:00
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz"
}
}
}
}
}
}
},
"jasmine-core": {
"version": "2.3.4",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"from": "https://registry.npmjs.org/jasmine-core/-/jasmine-core-2.3.4.tgz",
chore(testing): update karma-jasmine and jasmine Jasmine to jasmine-core 2.3.4. Update tools tests using minijasminenode to directly use jasmine. See #1860
2015-05-20 19:07:47 -04:00
"resolved": "https://registry.npmjs.org/jasmine-core/-/jasmine-core-2.3.4.tgz"
},
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"jpm": {
"version": "1.0.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/jpm/-/jpm-1.0.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/jpm/-/jpm-1.0.0.tgz",
"dependencies": {
"commander": {
"version": "2.6.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/commander/-/commander-2.6.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/commander/-/commander-2.6.0.tgz"
},
"fs-promise": {
"version": "0.3.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/fs-promise/-/fs-promise-0.3.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/fs-promise/-/fs-promise-0.3.1.tgz",
"dependencies": {
"any-promise": {
"version": "0.1.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/any-promise/-/any-promise-0.1.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/any-promise/-/any-promise-0.1.0.tgz"
}
}
},
"fs-extra": {
"version": "0.16.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/fs-extra/-/fs-extra-0.16.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-0.16.4.tgz",
"dependencies": {
"graceful-fs": {
"version": "3.0.8",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz"
},
"jsonfile": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.3",
"from": "https://registry.npmjs.org/jsonfile/-/jsonfile-2.2.3.tgz",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-2.2.3.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
},
"rimraf": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
},
"fx-runner": {
"version": "0.0.7",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/fx-runner/-/fx-runner-0.0.7.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/fx-runner/-/fx-runner-0.0.7.tgz",
"dependencies": {
"lodash": {
"version": "2.4.1",
fix(build): make dart formatter errors more readable Truncates the output to just the interesting parts
2015-05-27 21:53:49 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-2.4.1.tgz",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-2.4.1.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
},
"when": {
"version": "3.6.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/when/-/when-3.6.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/when/-/when-3.6.4.tgz"
},
"winreg": {
"version": "0.0.12",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/winreg/-/winreg-0.0.12.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/winreg/-/winreg-0.0.12.tgz"
}
}
},
"jpm-core": {
"version": "0.0.9",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/jpm-core/-/jpm-core-0.0.9.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/jpm-core/-/jpm-core-0.0.9.tgz"
},
"jetpack-id": {
"version": "0.0.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/jetpack-id/-/jetpack-id-0.0.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/jetpack-id/-/jetpack-id-0.0.4.tgz"
},
"jetpack-validation": {
"version": "0.0.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/jetpack-validation/-/jetpack-validation-0.0.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/jetpack-validation/-/jetpack-validation-0.0.4.tgz",
"dependencies": {
"resolve": {
"version": "0.7.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/resolve/-/resolve-0.7.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/resolve/-/resolve-0.7.4.tgz"
},
"semver": {
"version": "2.3.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/semver/-/semver-2.3.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/semver/-/semver-2.3.2.tgz"
}
}
},
"firefox-profile": {
"version": "0.3.9",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/firefox-profile/-/firefox-profile-0.3.9.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/firefox-profile/-/firefox-profile-0.3.9.tgz",
"dependencies": {
"adm-zip": {
"version": "0.4.7",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.7.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.7.tgz"
},
"archiver": {
"version": "0.14.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/archiver/-/archiver-0.14.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/archiver/-/archiver-0.14.4.tgz",
"dependencies": {
"buffer-crc32": {
"version": "0.2.5",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.5.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.5.tgz"
},
"glob": {
"version": "4.3.5",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
},
"lodash": {
"version": "3.2.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-3.2.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.2.0.tgz"
},
"readable-stream": {
"version": "1.0.33",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"tar-stream": {
"version": "1.1.5",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/tar-stream/-/tar-stream-1.1.5.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-1.1.5.tgz",
"dependencies": {
"bl": {
"version": "0.9.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz"
},
"end-of-stream": {
"version": "1.1.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz",
"dependencies": {
"once": {
"version": "1.3.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
},
"zip-stream": {
"version": "0.5.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/zip-stream/-/zip-stream-0.5.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/zip-stream/-/zip-stream-0.5.2.tgz",
"dependencies": {
"compress-commons": {
"version": "0.2.9",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/compress-commons/-/compress-commons-0.2.9.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/compress-commons/-/compress-commons-0.2.9.tgz",
"dependencies": {
"crc32-stream": {
"version": "0.3.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz"
},
"node-int64": {
"version": "0.3.3",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz"
}
}
}
}
}
}
},
"async": {
"version": "0.9.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.9.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
},
"lazystream": {
"version": "0.1.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/lazystream/-/lazystream-0.1.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/lazystream/-/lazystream-0.1.0.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
},
"lodash": {
"version": "3.5.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-3.5.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.5.0.tgz"
},
"wrench": {
"version": "1.5.8",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/wrench/-/wrench-1.5.8.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/wrench/-/wrench-1.5.8.tgz"
},
"xml2js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.15",
"from": "https://registry.npmjs.org/xml2js/-/xml2js-0.4.15.tgz",
"resolved": "https://registry.npmjs.org/xml2js/-/xml2js-0.4.15.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"dependencies": {
"sax": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.4",
"from": "https://registry.npmjs.org/sax/-/sax-1.1.4.tgz",
"resolved": "https://registry.npmjs.org/sax/-/sax-1.1.4.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
},
"xmlbuilder": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-4.0.0.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
},
"ini": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.3.4",
"from": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz",
"resolved": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
},
"jsontoxml": {
"version": "0.0.11",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/jsontoxml/-/jsontoxml-0.0.11.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/jsontoxml/-/jsontoxml-0.0.11.tgz"
},
"lodash": {
"version": "3.3.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-3.3.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.3.1.tgz"
},
"minimatch": {
"version": "2.0.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.4.tgz",
"dependencies": {
"brace-expansion": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
"from": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"dependencies": {
"balanced-match": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.2.1",
"from": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
},
"concat-map": {
"version": "0.0.1",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
}
}
}
}
},
"node-watch": {
"version": "0.3.4",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/node-watch/-/node-watch-0.3.4.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/node-watch/-/node-watch-0.3.4.tgz"
},
"tmp": {
"version": "0.0.25",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/tmp/-/tmp-0.0.25.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/tmp/-/tmp-0.0.25.tgz"
},
"open": {
"version": "0.0.5",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/open/-/open-0.0.5.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/open/-/open-0.0.5.tgz"
},
"promzard": {
"version": "0.3.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/promzard/-/promzard-0.3.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/promzard/-/promzard-0.3.0.tgz"
},
"read": {
"version": "1.0.5",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/read/-/read-1.0.5.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/read/-/read-1.0.5.tgz",
"dependencies": {
"mute-stream": {
"version": "0.0.5",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/mute-stream/-/mute-stream-0.0.5.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/mute-stream/-/mute-stream-0.0.5.tgz"
}
}
},
"semver": {
"version": "4.3.3",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/semver/-/semver-4.3.3.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/semver/-/semver-4.3.3.tgz"
},
"mozilla-version-comparator": {
"version": "1.0.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/mozilla-version-comparator/-/mozilla-version-comparator-1.0.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/mozilla-version-comparator/-/mozilla-version-comparator-1.0.2.tgz"
},
"mozilla-toolkit-versioning": {
"version": "0.0.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/mozilla-toolkit-versioning/-/mozilla-toolkit-versioning-0.0.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/mozilla-toolkit-versioning/-/mozilla-toolkit-versioning-0.0.2.tgz"
},
"when": {
"version": "3.7.2",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/when/-/when-3.7.2.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/when/-/when-3.7.2.tgz"
},
"zip-dir": {
"version": "1.0.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/zip-dir/-/zip-dir-1.0.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/zip-dir/-/zip-dir-1.0.0.tgz",
"dependencies": {
"jszip": {
"version": "2.5.0",
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"from": "https://registry.npmjs.org/jszip/-/jszip-2.5.0.tgz",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"resolved": "https://registry.npmjs.org/jszip/-/jszip-2.5.0.tgz",
"dependencies": {
"pako": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.2.8",
"from": "https://registry.npmjs.org/pako/-/pako-0.2.8.tgz",
"resolved": "https://registry.npmjs.org/pako/-/pako-0.2.8.tgz"
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
}
}
}
}
}
}
},
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"js-yaml": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.4.3",
"from": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.3.tgz",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.3.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
"argparse": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.3",
"from": "https://registry.npmjs.org/argparse/-/argparse-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.3.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
"lodash": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.10.1",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
},
"sprintf-js": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
}
}
},
"esprima": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.7.0",
"from": "https://registry.npmjs.org/esprima/-/esprima-2.7.0.tgz",
"resolved": "https://registry.npmjs.org/esprima/-/esprima-2.7.0.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
}
}
},
"karma": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.13.15",
"from": "https://registry.npmjs.org/karma/-/karma-0.13.15.tgz",
"resolved": "https://registry.npmjs.org/karma/-/karma-0.13.15.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"batch": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/batch/-/batch-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/batch/-/batch-0.5.3.tgz"
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"bluebird": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.10.2",
"from": "https://registry.npmjs.org/bluebird/-/bluebird-2.10.2.tgz",
"resolved": "https://registry.npmjs.org/bluebird/-/bluebird-2.10.2.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"body-parser": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.14.1",
"from": "https://registry.npmjs.org/body-parser/-/body-parser-1.14.1.tgz",
"resolved": "https://registry.npmjs.org/body-parser/-/body-parser-1.14.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"bytes": {
"version": "2.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/bytes/-/bytes-2.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/bytes/-/bytes-2.1.0.tgz"
},
"content-type": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/content-type/-/content-type-1.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/content-type/-/content-type-1.0.1.tgz"
},
"debug": {
"version": "2.2.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"ms": {
"version": "0.7.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"
}
}
},
"depd": {
"version": "1.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/depd/-/depd-1.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/depd/-/depd-1.1.0.tgz"
},
"http-errors": {
"version": "1.3.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/http-errors/-/http-errors-1.3.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/http-errors/-/http-errors-1.3.1.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"statuses": {
"version": "1.2.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/statuses/-/statuses-1.2.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/statuses/-/statuses-1.2.1.tgz"
}
}
},
"iconv-lite": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.12",
"from": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.4.12.tgz",
"resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.4.12.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"on-finished": {
"version": "2.3.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/on-finished/-/on-finished-2.3.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/on-finished/-/on-finished-2.3.0.tgz",
"dependencies": {
"ee-first": {
"version": "1.1.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz"
}
}
},
"qs": {
"version": "5.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/qs/-/qs-5.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/qs/-/qs-5.1.0.tgz"
},
"raw-body": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.4",
"from": "https://registry.npmjs.org/raw-body/-/raw-body-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/raw-body/-/raw-body-2.1.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"unpipe": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/unpipe/-/unpipe-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/unpipe/-/unpipe-1.0.0.tgz"
}
}
},
"type-is": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.6.9",
"from": "https://registry.npmjs.org/type-is/-/type-is-1.6.9.tgz",
"resolved": "https://registry.npmjs.org/type-is/-/type-is-1.6.9.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"media-typer": {
"version": "0.3.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/media-typer/-/media-typer-0.3.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/media-typer/-/media-typer-0.3.0.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"mime-types": {
"version": "2.1.7",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"mime-db": {
"version": "1.19.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"colors": {
"version": "1.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/colors/-/colors-1.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/colors/-/colors-1.1.2.tgz"
},
"connect": {
"version": "3.4.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/connect/-/connect-3.4.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/connect/-/connect-3.4.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"debug": {
"version": "2.2.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
"dependencies": {
"ms": {
"version": "0.7.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"finalhandler": {
"version": "0.4.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/finalhandler/-/finalhandler-0.4.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/finalhandler/-/finalhandler-0.4.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"escape-html": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/escape-html/-/escape-html-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/escape-html/-/escape-html-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"on-finished": {
"version": "2.3.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/on-finished/-/on-finished-2.3.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/on-finished/-/on-finished-2.3.0.tgz",
"dependencies": {
"ee-first": {
"version": "1.1.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz"
}
}
},
"unpipe": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/unpipe/-/unpipe-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/unpipe/-/unpipe-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"parseurl": {
"version": "1.3.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/parseurl/-/parseurl-1.3.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/parseurl/-/parseurl-1.3.0.tgz"
},
"utils-merge": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/utils-merge/-/utils-merge-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/utils-merge/-/utils-merge-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"core-js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.5",
"from": "https://registry.npmjs.org/core-js/-/core-js-1.2.5.tgz",
"resolved": "https://registry.npmjs.org/core-js/-/core-js-1.2.5.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"di": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/di/-/di-0.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/di/-/di-0.0.1.tgz"
},
"dom-serialize": {
"version": "2.2.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/dom-serialize/-/dom-serialize-2.2.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/dom-serialize/-/dom-serialize-2.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"custom-event": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/custom-event/-/custom-event-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/custom-event/-/custom-event-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"ent": {
"version": "2.2.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ent/-/ent-2.2.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ent/-/ent-2.2.0.tgz"
},
"extend": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/extend/-/extend-2.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/extend/-/extend-2.0.1.tgz"
},
"void-elements": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/void-elements/-/void-elements-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/void-elements/-/void-elements-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"expand-braces": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.2",
"from": "https://registry.npmjs.org/expand-braces/-/expand-braces-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/expand-braces/-/expand-braces-0.1.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"array-slice": {
"version": "0.2.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/array-slice/-/array-slice-0.2.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/array-slice/-/array-slice-0.2.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"array-unique": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/array-unique/-/array-unique-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/array-unique/-/array-unique-0.2.1.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"braces": {
"version": "0.1.5",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/braces/-/braces-0.1.5.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/braces/-/braces-0.1.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"expand-range": {
"version": "0.1.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/expand-range/-/expand-range-0.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/expand-range/-/expand-range-0.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"is-number": {
"version": "0.1.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/is-number/-/is-number-0.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/is-number/-/is-number-0.1.1.tgz"
},
"repeat-string": {
"version": "0.2.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/repeat-string/-/repeat-string-0.2.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-0.2.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"glob": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"inflight": {
"version": "1.0.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"graceful-fs": {
"version": "4.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"http-proxy": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.12.0",
"from": "https://registry.npmjs.org/http-proxy/-/http-proxy-1.12.0.tgz",
"resolved": "https://registry.npmjs.org/http-proxy/-/http-proxy-1.12.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"eventemitter3": {
"version": "1.1.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/eventemitter3/-/eventemitter3-1.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/eventemitter3/-/eventemitter3-1.1.1.tgz"
},
"requires-port": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/requires-port/-/requires-port-0.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/requires-port/-/requires-port-0.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"lodash": {
"version": "3.10.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"log4js": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "0.6.27",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/log4js/-/log4js-0.6.27.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/log4js/-/log4js-0.6.27.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"async": {
"version": "0.2.10",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
},
"readable-stream": {
"version": "1.0.33",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"underscore": {
"version": "1.8.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/underscore/-/underscore-1.8.2.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/underscore/-/underscore-1.8.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"mime": {
"version": "1.3.4",
"from": "https://registry.npmjs.org/mime/-/mime-1.3.4.tgz",
"resolved": "https://registry.npmjs.org/mime/-/mime-1.3.4.tgz"
},
"minimatch": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"brace-expansion": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"balanced-match": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"concat-map": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
}
}
},
"optimist": {
"version": "0.6.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
"dependencies": {
"wordwrap": {
"version": "0.0.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
},
"minimist": {
"version": "0.0.10",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz"
}
}
},
"rimraf": {
"version": "2.4.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz"
},
"socket.io": {
"version": "1.3.7",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/socket.io/-/socket.io-1.3.7.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/socket.io/-/socket.io-1.3.7.tgz",
"dependencies": {
"engine.io": {
"version": "1.5.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/engine.io/-/engine.io-1.5.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/engine.io/-/engine.io-1.5.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"base64id": {
"version": "0.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/base64id/-/base64id-0.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/base64id/-/base64id-0.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"debug": {
"version": "1.0.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-1.0.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-1.0.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"ms": {
"version": "0.6.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"engine.io-parser": {
"version": "1.2.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/engine.io-parser/-/engine.io-parser-1.2.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/engine.io-parser/-/engine.io-parser-1.2.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"after": {
"version": "0.8.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/after/-/after-0.8.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/after/-/after-0.8.1.tgz"
},
"arraybuffer.slice": {
"version": "0.0.6",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/arraybuffer.slice/-/arraybuffer.slice-0.0.6.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/arraybuffer.slice/-/arraybuffer.slice-0.0.6.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"base64-arraybuffer": {
"version": "0.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/base64-arraybuffer/-/base64-arraybuffer-0.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/base64-arraybuffer/-/base64-arraybuffer-0.1.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"blob": {
"version": "0.0.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/blob/-/blob-0.0.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/blob/-/blob-0.0.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"has-binary": {
"version": "0.1.6",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/has-binary/-/has-binary-0.1.6.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/has-binary/-/has-binary-0.1.6.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"utf8": {
"version": "2.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/utf8/-/utf8-2.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/utf8/-/utf8-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"ws": {
"version": "0.8.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ws/-/ws-0.8.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ws/-/ws-0.8.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"options": {
"version": "0.0.6",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/options/-/options-0.0.6.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/options/-/options-0.0.6.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"ultron": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ultron/-/ultron-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ultron/-/ultron-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"socket.io-parser": {
"version": "2.2.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-2.2.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-2.2.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"debug": {
"version": "0.7.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz"
},
"json3": {
"version": "3.2.6",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/json3/-/json3-3.2.6.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/json3/-/json3-3.2.6.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"component-emitter": {
"version": "1.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/component-emitter/-/component-emitter-1.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/component-emitter/-/component-emitter-1.1.2.tgz"
},
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"benchmark": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/benchmark/-/benchmark-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/benchmark/-/benchmark-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"socket.io-client": {
"version": "1.3.7",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/socket.io-client/-/socket.io-client-1.3.7.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/socket.io-client/-/socket.io-client-1.3.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"debug": {
"version": "0.7.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"engine.io-client": {
"version": "1.5.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/engine.io-client/-/engine.io-client-1.5.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/engine.io-client/-/engine.io-client-1.5.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"component-inherit": {
"version": "0.0.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/component-inherit/-/component-inherit-0.0.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/component-inherit/-/component-inherit-0.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"debug": {
"version": "1.0.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-1.0.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-1.0.4.tgz",
"dependencies": {
"ms": {
"version": "0.6.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz"
}
}
},
"engine.io-parser": {
"version": "1.2.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/engine.io-parser/-/engine.io-parser-1.2.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/engine.io-parser/-/engine.io-parser-1.2.2.tgz",
"dependencies": {
"after": {
"version": "0.8.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/after/-/after-0.8.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/after/-/after-0.8.1.tgz"
},
"arraybuffer.slice": {
"version": "0.0.6",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/arraybuffer.slice/-/arraybuffer.slice-0.0.6.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/arraybuffer.slice/-/arraybuffer.slice-0.0.6.tgz"
},
"base64-arraybuffer": {
"version": "0.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/base64-arraybuffer/-/base64-arraybuffer-0.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/base64-arraybuffer/-/base64-arraybuffer-0.1.2.tgz"
},
"blob": {
"version": "0.0.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/blob/-/blob-0.0.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/blob/-/blob-0.0.4.tgz"
},
"utf8": {
"version": "2.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/utf8/-/utf8-2.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/utf8/-/utf8-2.1.0.tgz"
}
}
},
"has-cors": {
"version": "1.0.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/has-cors/-/has-cors-1.0.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/has-cors/-/has-cors-1.0.3.tgz",
"dependencies": {
"global": {
"version": "2.0.1",
"from": "https://github.com/component/global/archive/v2.0.1.tar.gz",
"resolved": "https://github.com/component/global/archive/v2.0.1.tar.gz"
}
}
},
"parsejson": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/parsejson/-/parsejson-0.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/parsejson/-/parsejson-0.0.1.tgz",
"dependencies": {
"better-assert": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/better-assert/-/better-assert-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/better-assert/-/better-assert-1.0.2.tgz",
"dependencies": {
"callsite": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/callsite/-/callsite-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/callsite/-/callsite-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"parseqs": {
"version": "0.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/parseqs/-/parseqs-0.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/parseqs/-/parseqs-0.0.2.tgz",
"dependencies": {
"better-assert": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/better-assert/-/better-assert-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/better-assert/-/better-assert-1.0.2.tgz",
"dependencies": {
"callsite": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/callsite/-/callsite-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/callsite/-/callsite-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"parseuri": {
"version": "0.0.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/parseuri/-/parseuri-0.0.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/parseuri/-/parseuri-0.0.4.tgz",
"dependencies": {
"better-assert": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/better-assert/-/better-assert-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/better-assert/-/better-assert-1.0.2.tgz",
"dependencies": {
"callsite": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/callsite/-/callsite-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/callsite/-/callsite-1.0.0.tgz"
}
}
}
}
},
"ws": {
"version": "0.8.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ws/-/ws-0.8.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ws/-/ws-0.8.0.tgz",
"dependencies": {
"options": {
"version": "0.0.6",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/options/-/options-0.0.6.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/options/-/options-0.0.6.tgz"
},
"ultron": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ultron/-/ultron-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ultron/-/ultron-1.0.2.tgz"
}
}
},
"xmlhttprequest": {
"version": "1.5.0",
"from": "https://github.com/rase-/node-XMLHttpRequest/archive/a6b6f2.tar.gz",
"resolved": "https://github.com/rase-/node-XMLHttpRequest/archive/a6b6f2.tar.gz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"component-bind": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/component-bind/-/component-bind-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/component-bind/-/component-bind-1.0.0.tgz"
},
"component-emitter": {
"version": "1.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/component-emitter/-/component-emitter-1.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/component-emitter/-/component-emitter-1.1.2.tgz"
},
"object-component": {
"version": "0.0.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/object-component/-/object-component-0.0.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/object-component/-/object-component-0.0.3.tgz"
},
"has-binary": {
"version": "0.1.6",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/has-binary/-/has-binary-0.1.6.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/has-binary/-/has-binary-0.1.6.tgz",
"dependencies": {
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"indexof": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz"
},
"parseuri": {
"version": "0.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/parseuri/-/parseuri-0.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/parseuri/-/parseuri-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"better-assert": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/better-assert/-/better-assert-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/better-assert/-/better-assert-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"callsite": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/callsite/-/callsite-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/callsite/-/callsite-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"to-array": {
"version": "0.1.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/to-array/-/to-array-0.1.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/to-array/-/to-array-0.1.3.tgz"
},
"backo2": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/backo2/-/backo2-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/backo2/-/backo2-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"socket.io-adapter": {
"version": "0.3.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/socket.io-adapter/-/socket.io-adapter-0.3.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/socket.io-adapter/-/socket.io-adapter-0.3.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"debug": {
"version": "1.0.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-1.0.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-1.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"ms": {
"version": "0.6.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
}
}
},
"socket.io-parser": {
"version": "2.2.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-2.2.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-2.2.2.tgz",
"dependencies": {
"debug": {
"version": "0.7.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-0.7.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"json3": {
"version": "3.2.6",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/json3/-/json3-3.2.6.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/json3/-/json3-3.2.6.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"component-emitter": {
"version": "1.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/component-emitter/-/component-emitter-1.1.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/component-emitter/-/component-emitter-1.1.2.tgz"
},
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"benchmark": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/benchmark/-/benchmark-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/benchmark/-/benchmark-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"object-keys": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/object-keys/-/object-keys-1.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"has-binary-data": {
"version": "0.1.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/has-binary-data/-/has-binary-data-0.1.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/has-binary-data/-/has-binary-data-0.1.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"debug": {
"version": "2.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/debug/-/debug-2.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/debug/-/debug-2.1.0.tgz",
"dependencies": {
"ms": {
"version": "0.6.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ms/-/ms-0.6.2.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"source-map": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.3",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
},
"useragent": {
"version": "2.1.7",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/useragent/-/useragent-2.1.7.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/useragent/-/useragent-2.1.7.tgz",
"dependencies": {
"lru-cache": {
"version": "2.2.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.2.4.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.2.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"karma-browserstack-launcher": {
chore(package): update karma-browserstack-launcher to 0.1.7 Closes #5276
2015-11-13 11:09:38 -05:00
"version": "0.1.7",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"from": "https://registry.npmjs.org/karma-browserstack-launcher/-/karma-browserstack-launcher-0.1.7.tgz",
chore(package): update karma-browserstack-launcher to 0.1.7 Closes #5276
2015-11-13 11:09:38 -05:00
"resolved": "https://registry.npmjs.org/karma-browserstack-launcher/-/karma-browserstack-launcher-0.1.7.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"dependencies": {
"browserstack": {
"version": "1.2.0",
build(analytics): track bundle size This will send bundle sizes (before and after gzip) to Google Analytics so that we can track bundle size over time for every bundle we produce. Closes #5294
2015-11-15 05:27:59 -05:00
"from": "https://registry.npmjs.org/browserstack/-/browserstack-1.2.0.tgz",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"resolved": "https://registry.npmjs.org/browserstack/-/browserstack-1.2.0.tgz"
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"karma-chrome-launcher": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.2.1",
"from": "https://registry.npmjs.org/karma-chrome-launcher/-/karma-chrome-launcher-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/karma-chrome-launcher/-/karma-chrome-launcher-0.2.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"dependencies": {
"fs-access": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/fs-access/-/fs-access-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/fs-access/-/fs-access-1.0.0.tgz",
"dependencies": {
"null-check": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/null-check/-/null-check-1.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/null-check/-/null-check-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"karma-dart": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "0.3.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/karma-dart/-/karma-dart-0.3.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/karma-dart/-/karma-dart-0.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"dart2jsaas": {
"version": "0.0.16",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/dart2jsaas/-/dart2jsaas-0.0.16.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/dart2jsaas/-/dart2jsaas-0.0.16.tgz",
"dependencies": {
"mkdirp": {
"version": "0.3.5",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz"
},
"q": {
"version": "0.9.7",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/q/-/q-0.9.7.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/q/-/q-0.9.7.tgz"
},
"q-io": {
"version": "1.10.9",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/q-io/-/q-io-1.10.9.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/q-io/-/q-io-1.10.9.tgz",
"dependencies": {
"qs": {
"version": "0.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/qs/-/qs-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/qs/-/qs-0.1.0.tgz"
},
"url2": {
"version": "0.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/url2/-/url2-0.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/url2/-/url2-0.0.0.tgz"
},
"mime": {
"version": "1.2.11",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/mime/-/mime-1.2.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mime/-/mime-1.2.11.tgz"
},
"mimeparse": {
"version": "0.1.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/mimeparse/-/mimeparse-0.1.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/mimeparse/-/mimeparse-0.1.4.tgz"
},
"collections": {
"version": "0.2.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/collections/-/collections-0.2.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/collections/-/collections-0.2.2.tgz",
"dependencies": {
"weak-map": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/weak-map/-/weak-map-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/weak-map/-/weak-map-1.0.0.tgz"
}
}
}
}
}
}
}
}
},
"karma-jasmine": {
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"version": "0.3.6",
build(npm): update shrinkwrap with the missing hash-files dependency
2015-09-22 18:19:32 -04:00
"from": "https://registry.npmjs.org/karma-jasmine/-/karma-jasmine-0.3.6.tgz",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"resolved": "https://registry.npmjs.org/karma-jasmine/-/karma-jasmine-0.3.6.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"karma-sauce-launcher": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "0.2.14",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/karma-sauce-launcher/-/karma-sauce-launcher-0.2.14.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/karma-sauce-launcher/-/karma-sauce-launcher-0.2.14.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"dependencies": {
"wd": {
"version": "0.3.12",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/wd/-/wd-0.3.12.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/wd/-/wd-0.3.12.tgz",
"dependencies": {
"archiver": {
"version": "0.14.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/archiver/-/archiver-0.14.4.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/archiver/-/archiver-0.14.4.tgz",
"dependencies": {
"async": {
"version": "0.9.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.9.2.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
},
"buffer-crc32": {
"version": "0.2.5",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.5.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.5.tgz"
},
"glob": {
"version": "4.3.5",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
},
"lazystream": {
"version": "0.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lazystream/-/lazystream-0.1.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/lazystream/-/lazystream-0.1.0.tgz"
},
"lodash": {
"version": "3.2.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-3.2.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.2.0.tgz"
},
"readable-stream": {
"version": "1.0.33",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"tar-stream": {
"version": "1.1.5",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/tar-stream/-/tar-stream-1.1.5.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-1.1.5.tgz",
"dependencies": {
"bl": {
"version": "0.9.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz"
},
"end-of-stream": {
"version": "1.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.1.0.tgz",
"dependencies": {
"once": {
"version": "1.3.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
}
}
},
"zip-stream": {
"version": "0.5.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/zip-stream/-/zip-stream-0.5.2.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/zip-stream/-/zip-stream-0.5.2.tgz",
"dependencies": {
"compress-commons": {
"version": "0.2.9",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/compress-commons/-/compress-commons-0.2.9.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/compress-commons/-/compress-commons-0.2.9.tgz",
"dependencies": {
"crc32-stream": {
"version": "0.3.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz"
},
"node-int64": {
"version": "0.3.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz"
}
}
}
}
}
}
},
"async": {
"version": "1.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/async/-/async-1.0.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-1.0.0.tgz"
},
"lodash": {
"version": "3.9.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-3.9.3.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.9.3.tgz"
},
"q": {
"version": "1.4.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/q/-/q-1.4.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/q/-/q-1.4.1.tgz"
},
"request": {
"version": "2.55.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/request/-/request-2.55.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/request/-/request-2.55.0.tgz",
"dependencies": {
"bl": {
"version": "0.9.4",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
},
"caseless": {
"version": "0.9.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/caseless/-/caseless-0.9.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.9.0.tgz"
},
"forever-agent": {
"version": "0.6.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz"
},
"form-data": {
"version": "0.2.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/form-data/-/form-data-0.2.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/form-data/-/form-data-0.2.0.tgz",
"dependencies": {
"async": {
"version": "0.9.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.9.2.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
}
}
},
"json-stringify-safe": {
"version": "5.0.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
},
"mime-types": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.14",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"dependencies": {
"mime-db": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.12.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
}
}
},
"qs": {
"version": "2.4.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/qs/-/qs-2.4.2.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/qs/-/qs-2.4.2.tgz"
},
"tunnel-agent": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "0.4.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
"tough-cookie": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.0",
"from": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
"http-signature": {
"version": "0.10.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz",
"dependencies": {
"assert-plus": {
"version": "0.1.5",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
},
"asn1": {
"version": "0.1.11",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz"
},
"ctype": {
"version": "0.5.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz"
}
}
},
"oauth-sign": {
"version": "0.6.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.6.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.6.0.tgz"
},
"hawk": {
"version": "2.3.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/hawk/-/hawk-2.3.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/hawk/-/hawk-2.3.1.tgz",
"dependencies": {
"hoek": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.16.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
"boom": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.10.1",
"from": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz",
"resolved": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
"cryptiles": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.5",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
"sntp": {
"version": "1.0.9",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz"
}
}
},
"aws-sign2": {
"version": "0.5.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.5.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.5.0.tgz"
},
"stringstream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.0.5",
"from": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
"combined-stream": {
"version": "0.0.7",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/combined-stream/-/combined-stream-0.0.7.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-0.0.7.tgz",
"dependencies": {
"delayed-stream": {
"version": "0.0.5",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-0.0.5.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-0.0.5.tgz"
}
}
},
"isstream": {
"version": "0.1.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
},
"har-validator": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.8.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/har-validator/-/har-validator-1.8.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/har-validator/-/har-validator-1.8.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"dependencies": {
"bluebird": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.10.2",
"from": "https://registry.npmjs.org/bluebird/-/bluebird-2.10.2.tgz",
"resolved": "https://registry.npmjs.org/bluebird/-/bluebird-2.10.2.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
"chalk": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "1.1.1",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"dependencies": {
"ansi-styles": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.1.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
"escape-string-regexp": {
"version": "1.0.3",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"dependencies": {
"ansi-regex": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
}
}
},
"supports-color": {
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"version": "2.0.0",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"commander": {
"version": "2.9.0",
"from": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
"dependencies": {
"graceful-readlink": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz"
}
}
},
"is-my-json-valid": {
"version": "2.12.2",
"from": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
"resolved": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
"dependencies": {
"generate-function": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz"
},
"generate-object-property": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
"dependencies": {
"is-property": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz"
}
}
},
"jsonpointer": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz"
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
}
}
}
}
},
"underscore.string": {
"version": "3.0.3",
"from": "https://registry.npmjs.org/underscore.string/-/underscore.string-3.0.3.tgz",
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-3.0.3.tgz"
},
"vargs": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/vargs/-/vargs-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/vargs/-/vargs-0.1.0.tgz"
}
}
},
"sauce-connect-launcher": {
"version": "0.11.1",
"from": "https://registry.npmjs.org/sauce-connect-launcher/-/sauce-connect-launcher-0.11.1.tgz",
"resolved": "https://registry.npmjs.org/sauce-connect-launcher/-/sauce-connect-launcher-0.11.1.tgz",
"dependencies": {
"lodash": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.5.0.tgz"
},
"async": {
"version": "0.9.0",
"from": "https://registry.npmjs.org/async/-/async-0.9.0.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-0.9.0.tgz"
},
"adm-zip": {
"version": "0.4.7",
"from": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.7.tgz",
"resolved": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.7.tgz"
},
"rimraf": {
"version": "2.2.6",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.6.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.6.tgz"
}
}
},
"q": {
"version": "0.9.7",
"from": "https://registry.npmjs.org/q/-/q-0.9.7.tgz",
"resolved": "https://registry.npmjs.org/q/-/q-0.9.7.tgz"
},
"saucelabs": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/saucelabs/-/saucelabs-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/saucelabs/-/saucelabs-0.1.1.tgz"
}
}
},
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"karma-sourcemap-loader": {
"version": "0.3.6",
"from": "https://registry.npmjs.org/karma-sourcemap-loader/-/karma-sourcemap-loader-0.3.6.tgz",
"resolved": "https://registry.npmjs.org/karma-sourcemap-loader/-/karma-sourcemap-loader-0.3.6.tgz"
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash": {
"version": "2.4.2",
"from": "https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz"
},
"madge": {
"version": "0.5.0",
"from": "https://registry.npmjs.org/madge/-/madge-0.5.0.tgz",
"resolved": "https://registry.npmjs.org/madge/-/madge-0.5.0.tgz",
"dependencies": {
"amdetective": {
"version": "0.0.2",
"from": "https://registry.npmjs.org/amdetective/-/amdetective-0.0.2.tgz",
"resolved": "https://registry.npmjs.org/amdetective/-/amdetective-0.0.2.tgz",
"dependencies": {
"esprima": {
"version": "1.2.2",
"from": "https://registry.npmjs.org/esprima/-/esprima-1.2.2.tgz",
"resolved": "https://registry.npmjs.org/esprima/-/esprima-1.2.2.tgz"
}
}
},
"coffee-script": {
"version": "1.3.3",
"from": "https://registry.npmjs.org/coffee-script/-/coffee-script-1.3.3.tgz",
"resolved": "https://registry.npmjs.org/coffee-script/-/coffee-script-1.3.3.tgz"
},
"colors": {
"version": "0.6.0-1",
"from": "https://registry.npmjs.org/colors/-/colors-0.6.0-1.tgz",
"resolved": "https://registry.npmjs.org/colors/-/colors-0.6.0-1.tgz"
},
"commander": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/commander/-/commander-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/commander/-/commander-1.0.0.tgz"
},
"commondir": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/commondir/-/commondir-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/commondir/-/commondir-0.0.1.tgz"
},
"detective": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/detective/-/detective-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/detective/-/detective-0.1.1.tgz"
},
"detective-es6": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/detective-es6/-/detective-es6-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/detective-es6/-/detective-es6-1.1.0.tgz",
"dependencies": {
"node-source-walk": {
"version": "1.4.2",
"from": "https://registry.npmjs.org/node-source-walk/-/node-source-walk-1.4.2.tgz",
"resolved": "https://registry.npmjs.org/node-source-walk/-/node-source-walk-1.4.2.tgz",
"dependencies": {
"acorn": {
"version": "1.2.2",
"from": "https://registry.npmjs.org/acorn/-/acorn-1.2.2.tgz",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-1.2.2.tgz"
}
}
}
}
},
"graphviz": {
"version": "0.0.7",
"from": "https://registry.npmjs.org/graphviz/-/graphviz-0.0.7.tgz",
"resolved": "https://registry.npmjs.org/graphviz/-/graphviz-0.0.7.tgz",
"dependencies": {
"temp": {
"version": "0.4.0",
"from": "https://registry.npmjs.org/temp/-/temp-0.4.0.tgz",
"resolved": "https://registry.npmjs.org/temp/-/temp-0.4.0.tgz"
}
}
},
"react-tools": {
"version": "0.12.1",
"from": "https://registry.npmjs.org/react-tools/-/react-tools-0.12.1.tgz",
"resolved": "https://registry.npmjs.org/react-tools/-/react-tools-0.12.1.tgz",
"dependencies": {
"commoner": {
"version": "0.10.1",
"from": "https://registry.npmjs.org/commoner/-/commoner-0.10.1.tgz",
"resolved": "https://registry.npmjs.org/commoner/-/commoner-0.10.1.tgz",
"dependencies": {
"q": {
"version": "1.1.2",
"from": "https://registry.npmjs.org/q/-/q-1.1.2.tgz",
"resolved": "https://registry.npmjs.org/q/-/q-1.1.2.tgz"
},
"recast": {
"version": "0.9.11",
"from": "https://registry.npmjs.org/recast/-/recast-0.9.11.tgz",
"resolved": "https://registry.npmjs.org/recast/-/recast-0.9.11.tgz",
"dependencies": {
"esprima-fb": {
"version": "8001.1001.0-dev-harmony-fb",
"from": "https://registry.npmjs.org/esprima-fb/-/esprima-fb-8001.1001.0-dev-harmony-fb.tgz",
"resolved": "https://registry.npmjs.org/esprima-fb/-/esprima-fb-8001.1001.0-dev-harmony-fb.tgz"
},
"source-map": {
"version": "0.1.41",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.1.41.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.41.tgz",
"dependencies": {
"amdefine": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz"
}
}
},
"ast-types": {
"version": "0.6.7",
"from": "https://registry.npmjs.org/ast-types/-/ast-types-0.6.7.tgz",
"resolved": "https://registry.npmjs.org/ast-types/-/ast-types-0.6.7.tgz"
}
}
},
"commander": {
"version": "2.5.1",
"from": "https://registry.npmjs.org/commander/-/commander-2.5.1.tgz",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.5.1.tgz"
},
"graceful-fs": {
"version": "3.0.5",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.5.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.5.tgz"
},
"glob": {
"version": "4.2.2",
"from": "https://registry.npmjs.org/glob/-/glob-4.2.2.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-4.2.2.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"wrappy": {
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"minimatch": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-1.0.0.tgz",
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lru-cache": {
"version": "2.5.0",
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.5.0.tgz",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.5.0.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sigmund": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.0.tgz"
}
}
},
"once": {
"version": "1.3.1",
"from": "https://registry.npmjs.org/once/-/once-1.3.1.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.1.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
}
}
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"mkdirp": {
"version": "0.5.0",
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.0.tgz",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.0.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
},
"private": {
"version": "0.1.6",
"from": "https://registry.npmjs.org/private/-/private-0.1.6.tgz",
"resolved": "https://registry.npmjs.org/private/-/private-0.1.6.tgz"
},
"install": {
"version": "0.1.8",
"from": "https://registry.npmjs.org/install/-/install-0.1.8.tgz",
"resolved": "https://registry.npmjs.org/install/-/install-0.1.8.tgz"
},
"iconv-lite": {
"version": "0.4.5",
"from": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.4.5.tgz",
"resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.4.5.tgz"
}
}
},
"jstransform": {
"version": "8.2.0",
"from": "https://registry.npmjs.org/jstransform/-/jstransform-8.2.0.tgz",
"resolved": "https://registry.npmjs.org/jstransform/-/jstransform-8.2.0.tgz",
"dependencies": {
"base62": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/base62/-/base62-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/base62/-/base62-0.1.1.tgz"
},
"esprima-fb": {
"version": "8001.1001.0-dev-harmony-fb",
"from": "https://registry.npmjs.org/esprima-fb/-/esprima-fb-8001.1001.0-dev-harmony-fb.tgz",
"resolved": "https://registry.npmjs.org/esprima-fb/-/esprima-fb-8001.1001.0-dev-harmony-fb.tgz"
},
"source-map": {
"version": "0.1.31",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.1.31.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.31.tgz",
"dependencies": {
"amdefine": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz"
}
}
}
}
}
}
},
"resolve": {
"version": "0.2.3",
"from": "https://registry.npmjs.org/resolve/-/resolve-0.2.3.tgz",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-0.2.3.tgz"
},
"uglify-js": {
"version": "1.2.6",
"from": "https://registry.npmjs.org/uglify-js/-/uglify-js-1.2.6.tgz",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-1.2.6.tgz"
},
"walkdir": {
"version": "0.0.5",
"from": "https://registry.npmjs.org/walkdir/-/walkdir-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/walkdir/-/walkdir-0.0.5.tgz"
}
}
},
"merge": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/merge/-/merge-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/merge/-/merge-1.2.0.tgz"
},
"merge2": {
"version": "0.3.6",
"from": "https://registry.npmjs.org/merge2/-/merge2-0.3.6.tgz",
"resolved": "https://registry.npmjs.org/merge2/-/merge2-0.3.6.tgz"
},
"minimatch": {
"version": "2.0.10",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.10.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-2.0.10.tgz",
"dependencies": {
"brace-expansion": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.1.tgz",
"dependencies": {
"balanced-match": {
"version": "0.2.1",
"from": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-0.2.1.tgz"
},
"concat-map": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz"
}
}
}
}
},
"minimist": {
"version": "1.1.3",
"from": "https://registry.npmjs.org/minimist/-/minimist-1.1.3.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.1.3.tgz"
},
"mock-fs": {
"version": "2.7.1",
"from": "https://registry.npmjs.org/mock-fs/-/mock-fs-2.7.1.tgz",
"resolved": "https://registry.npmjs.org/mock-fs/-/mock-fs-2.7.1.tgz",
"dependencies": {
"rewire": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/rewire/-/rewire-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/rewire/-/rewire-2.0.1.tgz"
}
}
},
"node-uuid": {
"version": "1.4.3",
"from": "https://registry.npmjs.org/node-uuid/-/node-uuid-1.4.3.tgz",
"resolved": "https://registry.npmjs.org/node-uuid/-/node-uuid-1.4.3.tgz"
},
"on-headers": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/on-headers/-/on-headers-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/on-headers/-/on-headers-1.0.1.tgz"
},
"parse5": {
"version": "1.3.2",
"from": "https://registry.npmjs.org/parse5/-/parse5-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/parse5/-/parse5-1.3.2.tgz"
},
"protractor": {
"version": "2.5.1",
"from": "https://registry.npmjs.org/protractor/-/protractor-2.5.1.tgz",
"resolved": "https://registry.npmjs.org/protractor/-/protractor-2.5.1.tgz",
"dependencies": {
"request": {
"version": "2.57.0",
"from": "https://registry.npmjs.org/request/-/request-2.57.0.tgz",
"resolved": "https://registry.npmjs.org/request/-/request-2.57.0.tgz",
"dependencies": {
"bl": {
"version": "0.9.4",
"from": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
"resolved": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"caseless": {
"version": "0.10.0",
"from": "https://registry.npmjs.org/caseless/-/caseless-0.10.0.tgz",
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.10.0.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"forever-agent": {
"version": "0.6.1",
"from": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz",
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"form-data": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/form-data/-/form-data-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/form-data/-/form-data-0.2.0.tgz",
"dependencies": {
"async": {
"version": "0.9.2",
"from": "https://registry.npmjs.org/async/-/async-0.9.2.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
},
"combined-stream": {
"version": "0.0.7",
"from": "https://registry.npmjs.org/combined-stream/-/combined-stream-0.0.7.tgz",
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-0.0.7.tgz",
"dependencies": {
"delayed-stream": {
"version": "0.0.5",
"from": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-0.0.5.tgz"
}
}
}
}
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"json-stringify-safe": {
"version": "5.0.1",
"from": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
chore(package.json): add karma-sauce-launcher to dev dependencies Closes #2342
2015-06-04 06:34:43 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"mime-types": {
"version": "2.0.14",
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.0.14.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"mime-db": {
"version": "1.12.0",
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.12.0.tgz"
}
}
},
"qs": {
"version": "3.1.0",
"from": "https://registry.npmjs.org/qs/-/qs-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/qs/-/qs-3.1.0.tgz"
},
"tunnel-agent": {
"version": "0.4.1",
"from": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz",
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz"
},
"tough-cookie": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz"
},
"http-signature": {
"version": "0.11.0",
"from": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
"dependencies": {
"assert-plus": {
"version": "0.1.5",
"from": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz",
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
},
"asn1": {
"version": "0.1.11",
"from": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz",
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz"
},
"ctype": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz"
}
}
},
"oauth-sign": {
"version": "0.8.0",
"from": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz",
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz"
},
"hawk": {
"version": "2.3.1",
"from": "https://registry.npmjs.org/hawk/-/hawk-2.3.1.tgz",
"resolved": "https://registry.npmjs.org/hawk/-/hawk-2.3.1.tgz",
"dependencies": {
"hoek": {
"version": "2.16.3",
"from": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz",
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
},
"boom": {
"version": "2.10.1",
"from": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz",
"resolved": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz"
},
"cryptiles": {
"version": "2.0.5",
"from": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz",
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz"
},
"sntp": {
"version": "1.0.9",
"from": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz",
"resolved": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz"
}
}
},
"aws-sign2": {
"version": "0.5.0",
"from": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.5.0.tgz",
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.5.0.tgz"
},
"stringstream": {
"version": "0.0.5",
"from": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz"
},
"combined-stream": {
"version": "1.0.5",
"from": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
"dependencies": {
"delayed-stream": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"isstream": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
},
"har-validator": {
"version": "1.8.0",
"from": "https://registry.npmjs.org/har-validator/-/har-validator-1.8.0.tgz",
"resolved": "https://registry.npmjs.org/har-validator/-/har-validator-1.8.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"bluebird": {
"version": "2.10.2",
"from": "https://registry.npmjs.org/bluebird/-/bluebird-2.10.2.tgz",
"resolved": "https://registry.npmjs.org/bluebird/-/bluebird-2.10.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"chalk": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi-styles": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"escape-string-regexp": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"supports-color": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"commander": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.9.0",
"from": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
"dependencies": {
"graceful-readlink": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-my-json-valid": {
"version": "2.12.2",
"from": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
"resolved": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
"dependencies": {
"generate-function": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz"
},
"generate-object-property": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
"dependencies": {
"is-property": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz"
}
}
},
"jsonpointer": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz"
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
}
}
}
}
},
"selenium-webdriver": {
"version": "2.47.0",
"from": "https://registry.npmjs.org/selenium-webdriver/-/selenium-webdriver-2.47.0.tgz",
"resolved": "https://registry.npmjs.org/selenium-webdriver/-/selenium-webdriver-2.47.0.tgz",
"dependencies": {
"rimraf": {
"version": "2.4.3",
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"glob": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"inflight": {
"version": "1.0.4",
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.3.2",
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"wrappy": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"path-is-absolute": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
},
"tmp": {
"version": "0.0.24",
"from": "https://registry.npmjs.org/tmp/-/tmp-0.0.24.tgz",
"resolved": "https://registry.npmjs.org/tmp/-/tmp-0.0.24.tgz"
},
"ws": {
"version": "0.8.0",
"from": "https://registry.npmjs.org/ws/-/ws-0.8.0.tgz",
"resolved": "https://registry.npmjs.org/ws/-/ws-0.8.0.tgz",
"dependencies": {
"options": {
"version": "0.0.6",
"from": "https://registry.npmjs.org/options/-/options-0.0.6.tgz",
"resolved": "https://registry.npmjs.org/options/-/options-0.0.6.tgz"
},
"ultron": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/ultron/-/ultron-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/ultron/-/ultron-1.0.2.tgz"
}
}
},
"xml2js": {
"version": "0.4.4",
"from": "https://registry.npmjs.org/xml2js/-/xml2js-0.4.4.tgz",
"resolved": "https://registry.npmjs.org/xml2js/-/xml2js-0.4.4.tgz",
"dependencies": {
"sax": {
"version": "0.6.1",
"from": "https://registry.npmjs.org/sax/-/sax-0.6.1.tgz",
"resolved": "https://registry.npmjs.org/sax/-/sax-0.6.1.tgz"
},
"xmlbuilder": {
"version": "4.0.0",
"from": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-4.0.0.tgz",
"dependencies": {
"lodash": {
"version": "3.10.1",
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
}
}
}
}
}
}
},
"minijasminenode": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/minijasminenode/-/minijasminenode-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/minijasminenode/-/minijasminenode-1.1.1.tgz"
},
"jasminewd": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/jasminewd/-/jasminewd-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/jasminewd/-/jasminewd-1.1.0.tgz"
},
"jasminewd2": {
"version": "0.0.6",
"from": "https://registry.npmjs.org/jasminewd2/-/jasminewd2-0.0.6.tgz",
"resolved": "https://registry.npmjs.org/jasminewd2/-/jasminewd2-0.0.6.tgz"
},
"jasmine": {
"version": "2.3.2",
"from": "https://registry.npmjs.org/jasmine/-/jasmine-2.3.2.tgz",
"resolved": "https://registry.npmjs.org/jasmine/-/jasmine-2.3.2.tgz",
"dependencies": {
"exit": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz"
}
}
},
"saucelabs": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/saucelabs/-/saucelabs-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/saucelabs/-/saucelabs-1.0.1.tgz",
"dependencies": {
"https-proxy-agent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-1.0.0.tgz",
"dependencies": {
"agent-base": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/agent-base/-/agent-base-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/agent-base/-/agent-base-2.0.1.tgz",
"dependencies": {
"semver": {
"version": "5.0.3",
"from": "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz",
"resolved": "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"debug": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ms": {
"version": "0.7.1",
"from": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz",
"resolved": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"extend": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
}
}
},
"glob": {
"version": "3.2.11",
"from": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-3.2.11.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"minimatch": {
"version": "0.3.0",
"from": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-0.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lru-cache": {
"version": "2.7.0",
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.7.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sigmund": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"adm-zip": {
"version": "0.4.4",
"from": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.4.tgz",
"resolved": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.4.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"optimist": {
"version": "0.6.1",
"from": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"wordwrap": {
"version": "0.0.3",
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"minimist": {
"version": "0.0.10",
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"q": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/q/-/q-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/q/-/q-1.0.0.tgz"
},
"source-map-support": {
"version": "0.2.10",
"from": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.2.10.tgz",
"resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.2.10.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"source-map": {
"version": "0.1.32",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.1.32.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.32.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"amdefine": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
}
}
},
"html-entities": {
"version": "1.1.3",
"from": "https://registry.npmjs.org/html-entities/-/html-entities-1.1.3.tgz",
"resolved": "https://registry.npmjs.org/html-entities/-/html-entities-1.1.3.tgz"
},
"accessibility-developer-tools": {
"version": "2.6.0",
"from": "https://registry.npmjs.org/accessibility-developer-tools/-/accessibility-developer-tools-2.6.0.tgz",
"resolved": "https://registry.npmjs.org/accessibility-developer-tools/-/accessibility-developer-tools-2.6.0.tgz"
}
}
},
"proxy-middleware": {
"version": "0.13.1",
"from": "https://registry.npmjs.org/proxy-middleware/-/proxy-middleware-0.13.1.tgz",
"resolved": "https://registry.npmjs.org/proxy-middleware/-/proxy-middleware-0.13.1.tgz"
},
"q": {
"version": "1.4.1",
"from": "https://registry.npmjs.org/q/-/q-1.4.1.tgz",
"resolved": "https://registry.npmjs.org/q/-/q-1.4.1.tgz"
},
"react": {
"version": "0.14.2",
"from": "https://registry.npmjs.org/react/-/react-0.14.2.tgz",
"resolved": "https://registry.npmjs.org/react/-/react-0.14.2.tgz",
"dependencies": {
"envify": {
"version": "3.4.0",
"from": "https://registry.npmjs.org/envify/-/envify-3.4.0.tgz",
"resolved": "https://registry.npmjs.org/envify/-/envify-3.4.0.tgz",
"dependencies": {
"through": {
"version": "2.3.8",
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"jstransform": {
"version": "10.1.0",
"from": "https://registry.npmjs.org/jstransform/-/jstransform-10.1.0.tgz",
"resolved": "https://registry.npmjs.org/jstransform/-/jstransform-10.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"base62": {
"version": "0.1.1",
"from": "https://registry.npmjs.org/base62/-/base62-0.1.1.tgz",
"resolved": "https://registry.npmjs.org/base62/-/base62-0.1.1.tgz"
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"esprima-fb": {
"version": "13001.1001.0-dev-harmony-fb",
"from": "https://registry.npmjs.org/esprima-fb/-/esprima-fb-13001.1001.0-dev-harmony-fb.tgz",
"resolved": "https://registry.npmjs.org/esprima-fb/-/esprima-fb-13001.1001.0-dev-harmony-fb.tgz"
},
"source-map": {
"version": "0.1.31",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.1.31.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"amdefine": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
}
}
},
"fbjs": {
"version": "0.3.2",
"from": "https://registry.npmjs.org/fbjs/-/fbjs-0.3.2.tgz",
"resolved": "https://registry.npmjs.org/fbjs/-/fbjs-0.3.2.tgz",
"dependencies": {
"core-js": {
"version": "1.2.5",
"from": "https://registry.npmjs.org/core-js/-/core-js-1.2.5.tgz",
"resolved": "https://registry.npmjs.org/core-js/-/core-js-1.2.5.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"loose-envify": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/loose-envify/-/loose-envify-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/loose-envify/-/loose-envify-1.1.0.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"js-tokens": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/js-tokens/-/js-tokens-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-1.0.2.tgz"
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"promise": {
"version": "7.0.4",
"from": "https://registry.npmjs.org/promise/-/promise-7.0.4.tgz",
"resolved": "https://registry.npmjs.org/promise/-/promise-7.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"asap": {
"version": "2.0.3",
"from": "https://registry.npmjs.org/asap/-/asap-2.0.3.tgz",
"resolved": "https://registry.npmjs.org/asap/-/asap-2.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ua-parser-js": {
"version": "0.7.9",
"from": "https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.9.tgz",
"resolved": "https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.9.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"whatwg-fetch": {
"version": "0.9.0",
"from": "https://registry.npmjs.org/whatwg-fetch/-/whatwg-fetch-0.9.0.tgz",
"resolved": "https://registry.npmjs.org/whatwg-fetch/-/whatwg-fetch-0.9.0.tgz"
}
}
}
}
},
"reflect-metadata": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/reflect-metadata/-/reflect-metadata-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/reflect-metadata/-/reflect-metadata-0.1.2.tgz"
},
"rewire": {
"version": "2.3.4",
"from": "https://registry.npmjs.org/rewire/-/rewire-2.3.4.tgz",
"resolved": "https://registry.npmjs.org/rewire/-/rewire-2.3.4.tgz"
},
"run-sequence": {
"version": "1.1.4",
"from": "https://registry.npmjs.org/run-sequence/-/run-sequence-1.1.4.tgz",
"resolved": "https://registry.npmjs.org/run-sequence/-/run-sequence-1.1.4.tgz",
"dependencies": {
"chalk": {
"version": "1.1.1",
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"dependencies": {
"ansi-styles": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"strip-ansi": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"ansi-regex": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"supports-color": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
}
}
},
"gulp-util": {
"version": "3.0.7",
"from": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"resolved": "https://registry.npmjs.org/gulp-util/-/gulp-util-3.0.7.tgz",
"dependencies": {
"array-differ": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/array-differ/-/array-differ-1.0.0.tgz"
},
"array-uniq": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/array-uniq/-/array-uniq-1.0.2.tgz"
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"beeper": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/beeper/-/beeper-1.1.0.tgz"
},
"dateformat": {
"version": "1.0.11",
"from": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
"resolved": "https://registry.npmjs.org/dateformat/-/dateformat-1.0.11.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"get-stdin": {
"version": "5.0.0",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.0.tgz"
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"meow": {
"version": "3.5.0",
"from": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
"resolved": "https://registry.npmjs.org/meow/-/meow-3.5.0.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"camelcase-keys": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-1.0.0.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"camelcase": {
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"map-obj": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz"
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"loud-rejection": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/loud-rejection/-/loud-rejection-1.0.0.tgz"
},
"normalize-package-data": {
"version": "2.3.5",
"from": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.3.5.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"hosted-git-info": {
"version": "2.1.4",
"from": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.1.4.tgz"
},
"is-builtin-module": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"dependencies": {
"builtin-modules": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.0.tgz"
}
}
},
"validate-npm-package-license": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.1.tgz",
"dependencies": {
"spdx-correct": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-1.0.2.tgz",
"dependencies": {
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
},
"spdx-expression-parse": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-1.0.0.tgz",
"dependencies": {
"spdx-exceptions": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-1.0.3.tgz"
},
"spdx-license-ids": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-1.1.0.tgz"
}
}
}
}
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.0.1.tgz"
},
"read-pkg-up": {
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"version": "1.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"dependencies": {
"find-up": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.0.0.tgz",
"dependencies": {
"path-exists": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.0.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
},
"read-pkg": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"dependencies": {
"load-json-file": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.0.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"parse-json": {
"version": "2.2.0",
"from": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"dependencies": {
"error-ex": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.2.0.tgz"
}
}
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
"strip-bom": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"dependencies": {
"is-utf8": {
"version": "0.2.0",
"from": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.0.tgz"
}
}
}
}
},
"path-type": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.0.0.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
},
"pify": {
"version": "2.3.0",
"from": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz"
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
}
}
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"redent": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/redent/-/redent-1.0.0.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"indent-string": {
"version": "2.1.0",
"from": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-2.1.0.tgz",
"dependencies": {
"repeating": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/repeating/-/repeating-2.0.0.tgz",
"dependencies": {
"is-finite": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/is-finite/-/is-finite-1.0.1.tgz",
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.0.tgz"
}
}
}
}
}
}
},
"strip-indent": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-1.0.1.tgz",
"dependencies": {
"get-stdin": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-4.0.1.tgz"
}
}
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"trim-newlines": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz"
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"fancy-log": {
"version": "1.1.0",
"from": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.1.0.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"gulplog": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"glogg": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.0.tgz",
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"version": "1.0.0",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
}
}
}
}
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"has-gulplog": {
"version": "0.1.0",
"from": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
"resolved": "https://registry.npmjs.org/has-gulplog/-/has-gulplog-0.1.0.tgz",
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"sparkles": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.0.tgz"
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._reescape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reescape/-/lodash._reescape-3.0.0.tgz"
},
"lodash._reevaluate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reevaluate/-/lodash._reevaluate-3.0.0.tgz"
},
"lodash._reinterpolate": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._reinterpolate/-/lodash._reinterpolate-3.0.0.tgz"
},
"lodash.template": {
"version": "3.6.2",
"from": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.template/-/lodash.template-3.6.2.tgz",
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"lodash._basecopy": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basecopy/-/lodash._basecopy-3.0.1.tgz"
},
"lodash._basetostring": {
"version": "3.0.1",
"from": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._basetostring/-/lodash._basetostring-3.0.1.tgz"
},
"lodash._basevalues": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash._basevalues/-/lodash._basevalues-3.0.0.tgz"
},
"lodash._isiterateecall": {
"version": "3.0.9",
"from": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz",
"resolved": "https://registry.npmjs.org/lodash._isiterateecall/-/lodash._isiterateecall-3.0.9.tgz"
},
"lodash.escape": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.escape/-/lodash.escape-3.0.0.tgz"
},
"lodash.keys": {
"version": "3.1.2",
"from": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"resolved": "https://registry.npmjs.org/lodash.keys/-/lodash.keys-3.1.2.tgz",
"dependencies": {
"lodash._getnative": {
"version": "3.9.1",
"from": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz",
"resolved": "https://registry.npmjs.org/lodash._getnative/-/lodash._getnative-3.9.1.tgz"
},
"lodash.isarguments": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarguments/-/lodash.isarguments-3.0.4.tgz"
},
"lodash.isarray": {
"version": "3.0.4",
"from": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz",
"resolved": "https://registry.npmjs.org/lodash.isarray/-/lodash.isarray-3.0.4.tgz"
}
}
},
"lodash.restparam": {
"version": "3.6.1",
"from": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz",
"resolved": "https://registry.npmjs.org/lodash.restparam/-/lodash.restparam-3.6.1.tgz"
},
"lodash.templatesettings": {
"version": "3.1.0",
"from": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-3.1.0.tgz"
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"multipipe": {
"version": "0.1.2",
"from": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"resolved": "https://registry.npmjs.org/multipipe/-/multipipe-0.1.2.tgz",
"dependencies": {
"duplexer2": {
"version": "0.0.2",
"from": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"resolved": "https://registry.npmjs.org/duplexer2/-/duplexer2-0.0.2.tgz",
"dependencies": {
"readable-stream": {
"version": "1.1.13",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
}
}
}
}
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"object-assign": {
"version": "3.0.0",
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"replace-ext": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-0.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"through2": {
"version": "2.0.0",
"from": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"readable-stream": {
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"xtend": {
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"version": "4.0.1",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"vinyl": {
"version": "0.5.3",
"from": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-0.5.3.tgz",
"dependencies": {
"clone": {
"version": "1.0.2",
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
"clone-stats": {
"version": "0.0.1",
"from": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-0.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
refactor(facade): use rxjs package move to new RxJS distribution. BREAKING CHANGE: RxJS imports now are via `rxjs` instead of `@reactivex/rxjs` Individual operators can be imported `import 'rxjs/operators/map'`
2015-11-30 20:22:52 -05:00
"rxjs": {
"version": "5.0.0-alpha.11",
"from": "http://registry.npmjs.org/rxjs/-/rxjs-5.0.0-alpha.11.tgz",
"resolved": "http://registry.npmjs.org/rxjs/-/rxjs-5.0.0-alpha.11.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"selenium-webdriver": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.48.2",
"from": "https://registry.npmjs.org/selenium-webdriver/-/selenium-webdriver-2.48.2.tgz",
"resolved": "https://registry.npmjs.org/selenium-webdriver/-/selenium-webdriver-2.48.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"adm-zip": {
"version": "0.4.4",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/adm-zip/-/adm-zip-0.4.4.tgz"
},
"rimraf": {
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"version": "2.4.3",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.4.3.tgz",
"dependencies": {
"glob": {
"version": "5.0.15",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"tmp": {
"version": "0.0.24",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/tmp/-/tmp-0.0.24.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/tmp/-/tmp-0.0.24.tgz"
},
"ws": {
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"version": "0.8.0",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/ws/-/ws-0.8.0.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/ws/-/ws-0.8.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"options": {
"version": "0.0.6",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/options/-/options-0.0.6.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/options/-/options-0.0.6.tgz"
},
"ultron": {
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"version": "1.0.2",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/ultron/-/ultron-1.0.2.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/ultron/-/ultron-1.0.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"xml2js": {
"version": "0.4.4",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/xml2js/-/xml2js-0.4.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/xml2js/-/xml2js-0.4.4.tgz",
"dependencies": {
"sax": {
"version": "0.6.1",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/sax/-/sax-0.6.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/sax/-/sax-0.6.1.tgz"
},
"xmlbuilder": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.0.0",
"from": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-4.0.0.tgz",
"resolved": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-4.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"lodash": {
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"version": "3.10.1",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"from": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
}
}
},
build(gulp): check node and npm version and log a warning if incompatible Closes #1758
2015-05-08 01:37:35 -04:00
"semver": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "4.3.6",
"from": "https://registry.npmjs.org/semver/-/semver-4.3.6.tgz",
"resolved": "https://registry.npmjs.org/semver/-/semver-4.3.6.tgz"
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"sorted-object": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/sorted-object/-/sorted-object-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/sorted-object/-/sorted-object-1.0.0.tgz"
},
"source-map": {
"version": "0.3.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/source-map/-/source-map-0.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.3.0.tgz",
"dependencies": {
"amdefine": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"source-map-loader": {
"version": "0.1.5",
refactor(facade): use rxjs package move to new RxJS distribution. BREAKING CHANGE: RxJS imports now are via `rxjs` instead of `@reactivex/rxjs` Individual operators can be imported `import 'rxjs/operators/map'`
2015-11-30 20:22:52 -05:00
"from": "source-map-loader@>=0.1.5 <0.2.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"resolved": "https://registry.npmjs.org/source-map-loader/-/source-map-loader-0.1.5.tgz",
"dependencies": {
"loader-utils": {
"version": "0.2.12",
"from": "loader-utils@>=0.2.2 <0.3.0",
"resolved": "https://registry.npmjs.org/loader-utils/-/loader-utils-0.2.12.tgz",
"dependencies": {
"big.js": {
"version": "3.1.3",
"from": "big.js@>=3.0.2 <4.0.0",
"resolved": "https://registry.npmjs.org/big.js/-/big.js-3.1.3.tgz"
},
"json5": {
"version": "0.4.0",
"from": "json5@>=0.4.0 <0.5.0",
"resolved": "https://registry.npmjs.org/json5/-/json5-0.4.0.tgz"
}
}
},
"source-map": {
"version": "0.1.43",
"from": "source-map@>=0.1.33 <0.2.0",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.43.tgz",
"dependencies": {
"amdefine": {
"version": "1.0.0",
"from": "amdefine@>=0.0.4",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
}
}
},
"async": {
"version": "0.9.2",
"from": "async@>=0.9.0 <0.10.0",
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
}
}
},
fix(build): make dart formatter errors more readable Truncates the output to just the interesting parts
2015-05-27 21:53:49 -04:00
"strip-ansi": {
"version": "2.0.1",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-2.0.1.tgz",
fix(build): make dart formatter errors more readable Truncates the output to just the interesting parts
2015-05-27 21:53:49 -04:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-2.0.1.tgz",
"dependencies": {
"ansi-regex": {
"version": "1.1.1",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-1.1.1.tgz",
fix(build): make dart formatter errors more readable Truncates the output to just the interesting parts
2015-05-27 21:53:49 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-1.1.1.tgz"
}
}
},
build(broccoli): convert traceur and broccoli-dest-copy plugins to use tree-differ Also adding symlink-or-copy to our npm dependencies since our plugins now use it.
2015-04-24 14:00:15 -04:00
"symlink-or-copy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/symlink-or-copy/-/symlink-or-copy-1.0.1.tgz",
build(broccoli): convert traceur and broccoli-dest-copy plugins to use tree-differ Also adding symlink-or-copy to our npm dependencies since our plugins now use it.
2015-04-24 14:00:15 -04:00
"resolved": "https://registry.npmjs.org/symlink-or-copy/-/symlink-or-copy-1.0.1.tgz",
"dependencies": {
"copy-dereference": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/copy-dereference/-/copy-dereference-1.0.0.tgz",
build(broccoli): convert traceur and broccoli-dest-copy plugins to use tree-differ Also adding symlink-or-copy to our npm dependencies since our plugins now use it.
2015-04-24 14:00:15 -04:00
"resolved": "https://registry.npmjs.org/copy-dereference/-/copy-dereference-1.0.0.tgz"
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"systemjs": {
chore(npm): Upgrades systemjs dependency to 0.18.10.
2015-08-17 14:59:49 -04:00
"version": "0.18.10",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/systemjs/-/systemjs-0.18.10.tgz",
chore(npm): Upgrades systemjs dependency to 0.18.10.
2015-08-17 14:59:49 -04:00
"resolved": "https://registry.npmjs.org/systemjs/-/systemjs-0.18.10.tgz",
chore(npm): Upgrades systemjs to 0.18.3.
2015-08-14 18:05:56 -04:00
"dependencies": {
"es6-module-loader": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.17.8",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/es6-module-loader/-/es6-module-loader-0.17.8.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/es6-module-loader/-/es6-module-loader-0.17.8.tgz"
chore(npm): Upgrades systemjs to 0.18.3.
2015-08-14 18:05:56 -04:00
},
"when": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.7.4",
chore(browserstack): use patched karma launcher closes #5142
2015-11-06 04:55:04 -05:00
"from": "https://registry.npmjs.org/when/-/when-3.7.4.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/when/-/when-3.7.4.tgz"
chore(npm): Upgrades systemjs to 0.18.3.
2015-08-14 18:05:56 -04:00
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"systemjs-builder": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"version": "0.10.6",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/systemjs-builder/-/systemjs-builder-0.10.6.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/systemjs-builder/-/systemjs-builder-0.10.6.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"glob": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.0.15",
"from": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
"resolved": "https://registry.npmjs.org/glob/-/glob-5.0.15.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"inflight": {
"version": "1.0.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"path-is-absolute": {
"version": "1.0.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.0.tgz"
}
}
},
"mkdirp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.1",
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"minimist": {
"version": "0.0.8",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
},
"rsvp": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.1.0",
"from": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz",
"resolved": "https://registry.npmjs.org/rsvp/-/rsvp-3.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"source-map": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.4.4",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"amdefine": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"systemjs": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "0.16.11",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/systemjs/-/systemjs-0.16.11.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/systemjs/-/systemjs-0.16.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"es6-module-loader": {
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"version": "0.16.6",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/es6-module-loader/-/es6-module-loader-0.16.6.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/es6-module-loader/-/es6-module-loader-0.16.6.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"when": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "3.7.4",
"from": "https://registry.npmjs.org/when/-/when-3.7.4.tgz",
"resolved": "https://registry.npmjs.org/when/-/when-3.7.4.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
}
}
}
}
},
"traceur": {
"version": "0.0.88",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/traceur/-/traceur-0.0.88.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/traceur/-/traceur-0.0.88.tgz",
"dependencies": {
"commander": {
"version": "2.6.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/commander/-/commander-2.6.0.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/commander/-/commander-2.6.0.tgz"
},
"glob": {
"version": "4.3.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"version": "1.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
},
"semver": {
"version": "2.3.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/semver/-/semver-2.3.2.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/semver/-/semver-2.3.2.tgz"
},
"source-map-support": {
"version": "0.2.10",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.2.10.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.2.10.tgz",
"dependencies": {
"source-map": {
"version": "0.1.32",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/source-map/-/source-map-0.1.32.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.32.tgz",
"dependencies": {
"amdefine": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.0",
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
"uglify-js": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.5.0",
"from": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.5.0.tgz",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.5.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"async": {
"version": "0.2.10",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
},
"source-map": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.5.3",
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"uglify-to-browserify": {
"version": "1.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz",
chore(shrinkwrap): update dependencies to latest Also, our package.json was out-of-sync with npm-shrinkwrap.json; see https://github.com/angular/angular/issues/1737 This includes a fix for the shrinkwrapping of ts2dart; see https://github.com/angular/ts2dart/issues/138
2015-05-07 16:25:02 -04:00
"resolved": "https://registry.npmjs.org/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"yargs": {
"version": "3.5.4",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/yargs/-/yargs-3.5.4.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/yargs/-/yargs-3.5.4.tgz",
"dependencies": {
"camelcase": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.1",
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"decamelize": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.1",
"from": "https://registry.npmjs.org/decamelize/-/decamelize-1.1.1.tgz",
"resolved": "https://registry.npmjs.org/decamelize/-/decamelize-1.1.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"window-size": {
"version": "0.1.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/window-size/-/window-size-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/window-size/-/window-size-0.1.0.tgz"
},
"wordwrap": {
"version": "0.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz"
}
}
}
}
}
}
},
"through2": {
"version": "0.6.5",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/through2/-/through2-0.6.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/through2/-/through2-0.6.5.tgz",
"dependencies": {
"readable-stream": {
"version": "1.0.33",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"ts2dart": {
chore(ts2dart): update ts2dart to 0.7.14 Closes #5167
2015-11-06 19:45:14 -05:00
"version": "0.7.14",
chore(package): update karma-browserstack-launcher to 0.1.7 Closes #5276
2015-11-13 11:09:38 -05:00
"from": "https://registry.npmjs.org/ts2dart/-/ts2dart-0.7.14.tgz",
chore(ts2dart): update ts2dart to 0.7.14 Closes #5167
2015-11-06 19:45:14 -05:00
"resolved": "https://registry.npmjs.org/ts2dart/-/ts2dart-0.7.14.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
feat: upgrade t2dart to 0.6.8.
2015-07-02 05:33:21 -04:00
"source-map": {
feat: upgrade ts2dart to 0.6.9.
2015-07-14 12:54:33 -04:00
"version": "0.4.4",
chore(package): update karma-browserstack-launcher to 0.1.7 Closes #5276
2015-11-13 11:09:38 -05:00
"from": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
feat: upgrade ts2dart to 0.6.9.
2015-07-14 12:54:33 -04:00
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
feat: upgrade t2dart to 0.6.8.
2015-07-02 05:33:21 -04:00
"dependencies": {
"amdefine": {
feat: upgrade ts2dart to 0.6.9.
2015-07-14 12:54:33 -04:00
"version": "1.0.0",
chore(package): update karma-browserstack-launcher to 0.1.7 Closes #5276
2015-11-13 11:09:38 -05:00
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
feat: upgrade ts2dart to 0.6.9.
2015-07-14 12:54:33 -04:00
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
feat: upgrade t2dart to 0.6.8.
2015-07-02 05:33:21 -04:00
}
}
},
"source-map-support": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.3.3",
chore(package): update karma-browserstack-launcher to 0.1.7 Closes #5276
2015-11-13 11:09:38 -05:00
"from": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.3.3.tgz",
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.3.3.tgz",
feat: upgrade t2dart to 0.6.8.
2015-07-02 05:33:21 -04:00
"dependencies": {
"source-map": {
"version": "0.1.32",
chore(package): update karma-browserstack-launcher to 0.1.7 Closes #5276
2015-11-13 11:09:38 -05:00
"from": "https://registry.npmjs.org/source-map/-/source-map-0.1.32.tgz",
feat: upgrade t2dart to 0.6.8.
2015-07-02 05:33:21 -04:00
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.1.32.tgz",
chore(typing): use types for DOM API This is possible now that ts2dart special cases these for dart. Fixes #2770
2015-06-30 20:38:33 -04:00
"dependencies": {
feat: upgrade t2dart to 0.6.8.
2015-07-02 05:33:21 -04:00
"amdefine": {
feat: upgrade ts2dart to 0.6.9.
2015-07-14 12:54:33 -04:00
"version": "1.0.0",
chore(package): update karma-browserstack-launcher to 0.1.7 Closes #5276
2015-11-13 11:09:38 -05:00
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
feat: upgrade ts2dart to 0.6.9.
2015-07-14 12:54:33 -04:00
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
chore(typing): use types for DOM API This is possible now that ts2dart special cases these for dart. Fixes #2770
2015-06-30 20:38:33 -04:00
}
}
}
}
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
}
}
},
"tsd": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.6.5",
"from": "https://registry.npmjs.org/tsd/-/tsd-0.6.5.tgz",
"resolved": "https://registry.npmjs.org/tsd/-/tsd-0.6.5.tgz",
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"assertion-error": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/assertion-error/-/assertion-error-1.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/assertion-error/-/assertion-error-1.0.0.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"bl": {
"version": "0.9.4",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/bl/-/bl-0.9.4.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"readable-stream": {
"version": "1.0.33",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.0.33.tgz",
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"core-util-is": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"inherits": {
"version": "2.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
feat(decorators): adds decorators to be used by TS and Babel transpiled apps.
2015-04-28 21:17:00 -04:00
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"bluebird": {
"version": "1.2.4",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/bluebird/-/bluebird-1.2.4.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/bluebird/-/bluebird-1.2.4.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"chalk": {
"version": "1.1.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"dependencies": {
"ansi-styles": {
"version": "2.1.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"supports-color": {
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
}
}
},
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"colors": {
"version": "1.1.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/colors/-/colors-1.1.2.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/colors/-/colors-1.1.2.tgz"
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"deep-freeze": {
"version": "0.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/deep-freeze/-/deep-freeze-0.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/deep-freeze/-/deep-freeze-0.0.1.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"definition-header": {
"version": "0.1.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/definition-header/-/definition-header-0.1.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/definition-header/-/definition-header-0.1.0.tgz",
"dependencies": {
"parsimmon": {
"version": "0.5.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/parsimmon/-/parsimmon-0.5.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/parsimmon/-/parsimmon-0.5.1.tgz",
"dependencies": {
"pjs": {
"version": "5.1.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/pjs/-/pjs-5.1.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/pjs/-/pjs-5.1.1.tgz"
}
}
},
"xregexp": {
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/xregexp/-/xregexp-2.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/xregexp/-/xregexp-2.0.0.tgz"
}
}
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"detect-indent": {
"version": "0.2.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/detect-indent/-/detect-indent-0.2.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/detect-indent/-/detect-indent-0.2.0.tgz",
"dependencies": {
"get-stdin": {
"version": "0.1.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/get-stdin/-/get-stdin-0.1.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-0.1.0.tgz"
},
"minimist": {
"version": "0.1.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.1.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.1.0.tgz"
}
}
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"diff": {
"version": "1.4.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/diff/-/diff-1.4.0.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/diff/-/diff-1.4.0.tgz"
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"event-stream": {
"version": "3.1.7",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/event-stream/-/event-stream-3.1.7.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/event-stream/-/event-stream-3.1.7.tgz",
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"through": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "2.3.8",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
},
"duplexer": {
"version": "0.1.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/duplexer/-/duplexer-0.1.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/duplexer/-/duplexer-0.1.1.tgz"
},
"from": {
"version": "0.1.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/from/-/from-0.1.3.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/from/-/from-0.1.3.tgz"
},
"map-stream": {
"version": "0.1.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/map-stream/-/map-stream-0.1.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/map-stream/-/map-stream-0.1.0.tgz"
},
"pause-stream": {
"version": "0.0.11",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/pause-stream/-/pause-stream-0.0.11.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/pause-stream/-/pause-stream-0.0.11.tgz"
},
"split": {
"version": "0.2.10",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/split/-/split-0.2.10.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/split/-/split-0.2.10.tgz"
},
"stream-combiner": {
"version": "0.0.4",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/stream-combiner/-/stream-combiner-0.0.4.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/stream-combiner/-/stream-combiner-0.0.4.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"exit": {
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"version": "0.1.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"joi": {
"version": "4.9.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/joi/-/joi-4.9.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/joi/-/joi-4.9.0.tgz",
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"hoek": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.16.3",
"from": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz",
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"topo": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.0",
"from": "https://registry.npmjs.org/topo/-/topo-1.1.0.tgz",
"resolved": "https://registry.npmjs.org/topo/-/topo-1.1.0.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
},
"isemail": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.2.0",
"from": "https://registry.npmjs.org/isemail/-/isemail-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/isemail/-/isemail-1.2.0.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
},
"moment": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "2.10.6",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/moment/-/moment-2.10.6.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/moment/-/moment-2.10.6.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"joi-assert": {
"version": "0.0.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/joi-assert/-/joi-assert-0.0.3.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/joi-assert/-/joi-assert-0.0.3.tgz"
},
"jsesc": {
"version": "0.5.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/jsesc/-/jsesc-0.5.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/jsesc/-/jsesc-0.5.0.tgz"
},
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"json-pointer": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"version": "0.2.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/json-pointer/-/json-pointer-0.2.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/json-pointer/-/json-pointer-0.2.2.tgz",
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"dependencies": {
"foreach": {
"version": "2.0.5",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/foreach/-/foreach-2.0.5.tgz",
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"resolved": "https://registry.npmjs.org/foreach/-/foreach-2.0.5.tgz"
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"lazy.js": {
"version": "0.3.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/lazy.js/-/lazy.js-0.3.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/lazy.js/-/lazy.js-0.3.2.tgz"
},
"lru-cache": {
"version": "2.5.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.5.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-2.5.2.tgz"
},
"minimatch": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/minimatch/-/minimatch-1.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-1.0.0.tgz",
"dependencies": {
"sigmund": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/sigmund/-/sigmund-1.0.1.tgz"
}
}
},
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"ministyle": {
"version": "0.1.4",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ministyle/-/ministyle-0.1.4.tgz",
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"resolved": "https://registry.npmjs.org/ministyle/-/ministyle-0.1.4.tgz"
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"minitable": {
build(tsd): update tsd to v0.6.1 which is shrinkwrappable without fuss
2015-06-04 13:12:36 -04:00
"version": "0.0.4",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/minitable/-/minitable-0.0.4.tgz",
build(tsd): update tsd to v0.6.1 which is shrinkwrappable without fuss
2015-06-04 13:12:36 -04:00
"resolved": "https://registry.npmjs.org/minitable/-/minitable-0.0.4.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"minichain": {
"version": "0.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/minichain/-/minichain-0.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/minichain/-/minichain-0.0.1.tgz"
}
}
},
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
"miniwrite": {
"version": "0.1.4",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/miniwrite/-/miniwrite-0.1.4.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/miniwrite/-/miniwrite-0.1.4.tgz",
"dependencies": {
"mkdirp": {
"version": "0.3.5",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz"
}
}
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"mkdirp": {
"version": "0.5.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"open": {
"version": "0.0.5",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/open/-/open-0.0.5.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/open/-/open-0.0.5.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"request": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.65.0",
"from": "https://registry.npmjs.org/request/-/request-2.65.0.tgz",
"resolved": "https://registry.npmjs.org/request/-/request-2.65.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"bl": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
"dependencies": {
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
},
"string_decoder": {
"version": "0.10.31",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
}
}
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"caseless": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "0.11.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"extend": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "3.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz"
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"forever-agent": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"version": "0.6.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"form-data": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "1.0.0-rc3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"async": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.5.0",
"from": "https://registry.npmjs.org/async/-/async-1.5.0.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-1.5.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"json-stringify-safe": {
"version": "5.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
},
"mime-types": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.1.7",
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"mime-db": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.19.0",
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
}
}
},
"qs": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "5.2.0",
"from": "https://registry.npmjs.org/qs/-/qs-5.2.0.tgz",
"resolved": "https://registry.npmjs.org/qs/-/qs-5.2.0.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"tunnel-agent": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "0.4.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
},
"tough-cookie": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.2.0",
"from": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz",
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"http-signature": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"version": "0.11.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"assert-plus": {
"version": "0.1.5",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
},
"asn1": {
"version": "0.1.11",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz"
},
"ctype": {
"version": "0.5.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz"
}
}
},
"oauth-sign": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"version": "0.8.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"hawk": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "3.1.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/hawk/-/hawk-3.1.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/hawk/-/hawk-3.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
"hoek": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.16.3",
"from": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz",
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"boom": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.10.1",
"from": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz",
"resolved": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"cryptiles": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.5",
"from": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz",
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"sntp": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"version": "1.0.9",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"aws-sign2": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.6.0",
"from": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.6.0.tgz",
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.6.0.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"stringstream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.0.5",
"from": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"combined-stream": {
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"version": "1.0.5",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"delayed-stream": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz"
}
}
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"isstream": {
"version": "0.1.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
feat(benchmark): added an implementation of the tree benchmark in React
2015-04-29 21:11:56 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"har-validator": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.2",
"from": "https://registry.npmjs.org/har-validator/-/har-validator-2.0.2.tgz",
"resolved": "https://registry.npmjs.org/har-validator/-/har-validator-2.0.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"commander": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.9.0",
"from": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"graceful-readlink": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz"
}
}
},
"is-my-json-valid": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "2.12.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"generate-function": {
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz"
},
"generate-object-property": {
"version": "1.2.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
"dependencies": {
"is-property": {
"version": "1.0.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz"
}
}
},
"jsonpointer": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz"
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
}
}
},
"pinkie-promise": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"rimraf": {
"version": "2.2.8",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.2.8.tgz"
},
"type-detect": {
"version": "0.1.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/type-detect/-/type-detect-0.1.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/type-detect/-/type-detect-0.1.2.tgz"
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"update-notifier": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"version": "0.2.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/update-notifier/-/update-notifier-0.2.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/update-notifier/-/update-notifier-0.2.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"chalk": {
"version": "0.5.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/chalk/-/chalk-0.5.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/chalk/-/chalk-0.5.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"ansi-styles": {
"version": "1.1.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-1.1.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-1.1.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"escape-string-regexp": {
"version": "1.0.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"has-ansi": {
"version": "0.1.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-0.1.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-0.1.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"ansi-regex": {
"version": "0.2.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"strip-ansi": {
"version": "0.3.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-0.3.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-0.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"ansi-regex": {
"version": "0.2.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-0.2.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"supports-color": {
"version": "0.2.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/supports-color/-/supports-color-0.2.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-0.2.0.tgz"
}
}
},
"configstore": {
"version": "0.3.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/configstore/-/configstore-0.3.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/configstore/-/configstore-0.3.2.tgz",
"dependencies": {
"graceful-fs": {
"version": "3.0.8",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-3.0.8.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"object-assign": {
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"version": "2.1.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/object-assign/-/object-assign-2.1.1.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-2.1.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"osenv": {
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"version": "0.1.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/osenv/-/osenv-0.1.3.tgz",
"dependencies": {
"os-homedir": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/os-homedir/-/os-homedir-1.0.1.tgz"
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
},
"os-tmpdir": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/os-tmpdir/-/os-tmpdir-1.0.1.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"user-home": {
"version": "1.1.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/user-home/-/user-home-1.1.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/user-home/-/user-home-1.1.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"xdg-basedir": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/xdg-basedir/-/xdg-basedir-1.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/xdg-basedir/-/xdg-basedir-1.0.1.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"is-npm": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/is-npm/-/is-npm-1.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/is-npm/-/is-npm-1.0.0.tgz"
},
"latest-version": {
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/latest-version/-/latest-version-1.0.1.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/latest-version/-/latest-version-1.0.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"package-json": {
build(tsd): update tsd to v0.6.1 which is shrinkwrappable without fuss
2015-06-04 13:12:36 -04:00
"version": "1.2.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/package-json/-/package-json-1.2.0.tgz",
build(tsd): update tsd to v0.6.1 which is shrinkwrappable without fuss
2015-06-04 13:12:36 -04:00
"resolved": "https://registry.npmjs.org/package-json/-/package-json-1.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"got": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "3.3.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/got/-/got-3.3.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/got/-/got-3.3.1.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"duplexify": {
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"version": "3.4.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/duplexify/-/duplexify-3.4.2.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/duplexify/-/duplexify-3.4.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"end-of-stream": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.0.0.tgz",
"dependencies": {
"once": {
"version": "1.3.2",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
},
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"inherits": {
"version": "2.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"isarray": {
"version": "0.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"process-nextick-args": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"string_decoder": {
"version": "0.10.31",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"util-deprecate": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"infinity-agent": {
"version": "2.0.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/infinity-agent/-/infinity-agent-2.0.3.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/infinity-agent/-/infinity-agent-2.0.3.tgz"
},
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"is-redirect": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/is-redirect/-/is-redirect-1.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/is-redirect/-/is-redirect-1.0.0.tgz"
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"is-stream": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/is-stream/-/is-stream-1.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/is-stream/-/is-stream-1.0.1.tgz"
},
"lowercase-keys": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-1.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-1.0.0.tgz"
},
"nested-error-stacks": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/nested-error-stacks/-/nested-error-stacks-1.0.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/nested-error-stacks/-/nested-error-stacks-1.0.1.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
},
"object-assign": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "3.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-3.0.0.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
},
"prepend-http": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.3",
"from": "https://registry.npmjs.org/prepend-http/-/prepend-http-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/prepend-http/-/prepend-http-1.0.3.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
},
"read-all-stream": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "3.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/read-all-stream/-/read-all-stream-3.0.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/read-all-stream/-/read-all-stream-3.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"pinkie-promise": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"inherits": {
"version": "2.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"isarray": {
"version": "0.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"process-nextick-args": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.3",
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"string_decoder": {
"version": "0.10.31",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"util-deprecate": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.0.2",
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
}
}
}
}
},
"timed-out": {
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/timed-out/-/timed-out-2.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/timed-out/-/timed-out-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"registry-url": {
"version": "3.0.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/registry-url/-/registry-url-3.0.3.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/registry-url/-/registry-url-3.0.3.tgz",
"dependencies": {
"rc": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.1.2",
"from": "https://registry.npmjs.org/rc/-/rc-1.1.2.tgz",
"resolved": "https://registry.npmjs.org/rc/-/rc-1.1.2.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"dependencies": {
"deep-extend": {
"version": "0.2.11",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/deep-extend/-/deep-extend-0.2.11.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/deep-extend/-/deep-extend-0.2.11.tgz"
},
"strip-json-comments": {
"version": "0.1.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-0.1.3.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-0.1.3.tgz"
},
"ini": {
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"version": "1.3.4",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz",
fix(build): Reduce rx typings to what we actually require. This should help a lot with github rate limiting by removing about 2/3 of the dependencies.
2015-06-29 18:30:48 -04:00
"resolved": "https://registry.npmjs.org/ini/-/ini-1.3.4.tgz"
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"semver-diff": {
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/semver-diff/-/semver-diff-2.0.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/semver-diff/-/semver-diff-2.0.0.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"string-length": {
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"version": "1.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/string-length/-/string-length-1.0.1.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/string-length/-/string-length-1.0.1.tgz",
"dependencies": {
"strip-ansi": {
"version": "3.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
fix(build): delete unreferenced typings on npm install fixes #1636 Closes #3940
2015-09-01 12:58:36 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"uri-templates": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.1.9",
"from": "https://registry.npmjs.org/uri-templates/-/uri-templates-0.1.9.tgz",
"resolved": "https://registry.npmjs.org/uri-templates/-/uri-templates-0.1.9.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
"uuid": {
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"version": "2.0.1",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/uuid/-/uuid-2.0.1.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/uuid/-/uuid-2.0.1.tgz"
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
},
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"verror": {
"version": "1.4.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/verror/-/verror-1.4.0.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/verror/-/verror-1.4.0.tgz",
"dependencies": {
"extsprintf": {
"version": "1.0.3",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"from": "https://registry.npmjs.org/extsprintf/-/extsprintf-1.0.3.tgz",
chore(deps): bumps up deps on tsd and ts2dart.
2015-06-03 17:26:33 -04:00
"resolved": "https://registry.npmjs.org/extsprintf/-/extsprintf-1.0.3.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"tslint": {
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"version": "3.0.0-dev.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/tslint/-/tslint-3.0.0-dev.1.tgz",
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
"resolved": "https://registry.npmjs.org/tslint/-/tslint-3.0.0-dev.1.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"dependencies": {
"findup-sync": {
"version": "0.2.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.2.1.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-0.2.1.tgz",
"dependencies": {
"glob": {
"version": "4.3.5",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/glob/-/glob-4.3.5.tgz",
"dependencies": {
"inflight": {
"version": "1.0.4",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.4.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
},
"inherits": {
"version": "2.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"once": {
"version": "1.3.2",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/once/-/once-1.3.2.tgz",
"dependencies": {
"wrappy": {
"version": "1.0.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.1.tgz"
}
}
}
}
}
}
},
"optimist": {
"version": "0.6.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
"dependencies": {
"wordwrap": {
"version": "0.0.3",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
},
"minimist": {
"version": "0.0.10",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz"
}
}
},
"underscore.string": {
"version": "3.1.1",
chore(dgeni): clean up legacy typings bundle creation Fixes #4967 Closes #4991
2015-10-28 18:22:40 -04:00
"from": "https://registry.npmjs.org/underscore.string/-/underscore.string-3.1.1.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-3.1.1.tgz"
chore(tslint): disallow variable names that look like keywords. We've had issues such as the one I documented: https://github.com/Microsoft/TypeScript/issues/5187 This tslint check prevents this happening again. This change also updates to the newest tslint which gets typings from npm. Closes #4970
2015-10-27 23:51:03 -04:00
},
"typescript": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.8.0-dev.20151103",
"from": "https://registry.npmjs.org/typescript/-/typescript-1.8.0-dev.20151103.tgz",
"resolved": "https://registry.npmjs.org/typescript/-/typescript-1.8.0-dev.20151103.tgz"
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
}
}
},
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"typescript": {
chore(typescript 1.6 upgrade): fix build.tools
2015-09-22 15:03:39 -04:00
"version": "1.6.2",
build(npm): upgrade gulp-sass to v2.0.4
2015-09-25 19:05:31 -04:00
"from": "https://registry.npmjs.org/typescript/-/typescript-1.6.2.tgz",
chore(typescript): fixes dart failures and linter Closes #4359
2015-09-25 15:58:00 -04:00
"resolved": "https://registry.npmjs.org/typescript/-/typescript-1.6.2.tgz"
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
},
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"universal-analytics": {
"version": "0.3.9",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/universal-analytics/-/universal-analytics-0.3.9.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/universal-analytics/-/universal-analytics-0.3.9.tgz",
"dependencies": {
"request": {
"version": "2.65.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/request/-/request-2.65.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/request/-/request-2.65.0.tgz",
"dependencies": {
"bl": {
"version": "1.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/bl/-/bl-1.0.0.tgz",
"dependencies": {
"readable-stream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.0.4",
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.0.4.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"process-nextick-args": {
"version": "1.0.3",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.3.tgz"
},
"string_decoder": {
"version": "0.10.31",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"util-deprecate": {
"version": "1.0.2",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
}
}
}
}
},
"caseless": {
"version": "0.11.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/caseless/-/caseless-0.11.0.tgz"
},
"extend": {
"version": "3.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/extend/-/extend-3.0.0.tgz"
},
"forever-agent": {
"version": "0.6.1",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz"
},
"form-data": {
"version": "1.0.0-rc3",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/form-data/-/form-data-1.0.0-rc3.tgz",
"dependencies": {
"async": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "1.5.0",
"from": "https://registry.npmjs.org/async/-/async-1.5.0.tgz",
"resolved": "https://registry.npmjs.org/async/-/async-1.5.0.tgz"
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
}
}
},
"json-stringify-safe": {
"version": "5.0.1",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz"
},
"mime-types": {
"version": "2.1.7",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.7.tgz",
"dependencies": {
"mime-db": {
"version": "1.19.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.19.0.tgz"
}
}
},
"qs": {
"version": "5.2.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/qs/-/qs-5.2.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/qs/-/qs-5.2.0.tgz"
},
"tunnel-agent": {
"version": "0.4.1",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.1.tgz"
},
"tough-cookie": {
"version": "2.2.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.0.tgz"
},
"http-signature": {
"version": "0.11.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/http-signature/-/http-signature-0.11.0.tgz",
"dependencies": {
"assert-plus": {
"version": "0.1.5",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-0.1.5.tgz"
},
"asn1": {
"version": "0.1.11",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/asn1/-/asn1-0.1.11.tgz"
},
"ctype": {
"version": "0.5.3",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/ctype/-/ctype-0.5.3.tgz"
}
}
},
"oauth-sign": {
"version": "0.8.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.0.tgz"
},
"hawk": {
"version": "3.1.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/hawk/-/hawk-3.1.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/hawk/-/hawk-3.1.0.tgz",
"dependencies": {
"hoek": {
"version": "2.16.3",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"
},
"boom": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.10.1",
"from": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz",
"resolved": "https://registry.npmjs.org/boom/-/boom-2.10.1.tgz"
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
},
"cryptiles": {
"version": "2.0.5",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz"
},
"sntp": {
"version": "1.0.9",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/sntp/-/sntp-1.0.9.tgz"
}
}
},
"aws-sign2": {
"version": "0.6.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.6.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.6.0.tgz"
},
"stringstream": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "0.0.5",
"from": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz",
"resolved": "https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz"
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
},
"combined-stream": {
"version": "1.0.5",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz",
"dependencies": {
"delayed-stream": {
"version": "1.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz"
}
}
},
"isstream": {
"version": "0.1.2",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz"
},
"har-validator": {
"version": "2.0.2",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/har-validator/-/har-validator-2.0.2.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/har-validator/-/har-validator-2.0.2.tgz",
"dependencies": {
"chalk": {
"version": "1.1.1",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/chalk/-/chalk-1.1.1.tgz",
"dependencies": {
"ansi-styles": {
"version": "2.1.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-2.1.0.tgz"
},
"escape-string-regexp": {
"version": "1.0.3",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.3.tgz"
},
"has-ansi": {
"version": "2.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/has-ansi/-/has-ansi-2.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"strip-ansi": {
"version": "3.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.0.tgz",
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.0.0.tgz"
}
}
},
"supports-color": {
"version": "2.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz"
}
}
},
"commander": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"version": "2.9.0",
"from": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.9.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"dependencies": {
"graceful-readlink": {
"version": "1.0.1",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz"
}
}
},
"is-my-json-valid": {
"version": "2.12.2",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.12.2.tgz",
"dependencies": {
"generate-function": {
"version": "2.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/generate-function/-/generate-function-2.0.0.tgz"
},
"generate-object-property": {
"version": "1.2.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/generate-object-property/-/generate-object-property-1.2.0.tgz",
"dependencies": {
"is-property": {
"version": "1.0.2",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz"
}
}
},
"jsonpointer": {
"version": "2.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/jsonpointer/-/jsonpointer-2.0.0.tgz"
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
},
"xtend": {
"version": "4.0.1",
"from": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz"
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
}
}
},
"pinkie-promise": {
"version": "1.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-1.0.0.tgz",
"dependencies": {
"pinkie": {
"version": "1.0.0",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-1.0.0.tgz"
}
}
}
}
}
}
},
"underscore": {
"version": "1.8.3",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/underscore/-/underscore-1.8.3.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/underscore/-/underscore-1.8.3.tgz"
},
"async": {
"version": "0.2.10",
chore(package): update RxJS dependency version
2015-10-15 17:16:01 -04:00
"from": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
}
}
},
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"webpack": {
"version": "1.12.6",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/webpack/-/webpack-1.12.6.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/webpack/-/webpack-1.12.6.tgz",
"dependencies": {
"async": {
"version": "1.5.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/async/-/async-1.5.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/async/-/async-1.5.0.tgz"
},
"clone": {
"version": "1.0.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/clone/-/clone-1.0.2.tgz"
},
"enhanced-resolve": {
"version": "0.9.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-0.9.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-0.9.1.tgz",
"dependencies": {
"graceful-fs": {
"version": "4.1.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
}
}
},
"esprima": {
"version": "2.7.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/esprima/-/esprima-2.7.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/esprima/-/esprima-2.7.0.tgz"
},
"interpret": {
"version": "0.6.6",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/interpret/-/interpret-0.6.6.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/interpret/-/interpret-0.6.6.tgz"
},
"loader-utils": {
"version": "0.2.11",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/loader-utils/-/loader-utils-0.2.11.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/loader-utils/-/loader-utils-0.2.11.tgz",
"dependencies": {
"big.js": {
"version": "3.1.3",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/big.js/-/big.js-3.1.3.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/big.js/-/big.js-3.1.3.tgz"
},
"json5": {
"version": "0.4.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/json5/-/json5-0.4.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/json5/-/json5-0.4.0.tgz"
}
}
},
"memory-fs": {
"version": "0.2.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/memory-fs/-/memory-fs-0.2.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/memory-fs/-/memory-fs-0.2.0.tgz"
},
"mkdirp": {
"version": "0.5.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
"dependencies": {
"minimist": {
"version": "0.0.8",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz"
}
}
},
"node-libs-browser": {
"version": "0.5.3",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/node-libs-browser/-/node-libs-browser-0.5.3.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/node-libs-browser/-/node-libs-browser-0.5.3.tgz",
"dependencies": {
"assert": {
"version": "1.3.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/assert/-/assert-1.3.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/assert/-/assert-1.3.0.tgz"
},
"browserify-zlib": {
"version": "0.1.4",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/browserify-zlib/-/browserify-zlib-0.1.4.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/browserify-zlib/-/browserify-zlib-0.1.4.tgz",
"dependencies": {
"pako": {
"version": "0.2.8",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/pako/-/pako-0.2.8.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/pako/-/pako-0.2.8.tgz"
}
}
},
"buffer": {
"version": "3.5.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/buffer/-/buffer-3.5.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/buffer/-/buffer-3.5.2.tgz",
"dependencies": {
"ieee754": {
"version": "1.1.6",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/ieee754/-/ieee754-1.1.6.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/ieee754/-/ieee754-1.1.6.tgz"
},
"is-array": {
"version": "1.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/is-array/-/is-array-1.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/is-array/-/is-array-1.0.1.tgz"
}
}
},
"console-browserify": {
"version": "1.1.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/console-browserify/-/console-browserify-1.1.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/console-browserify/-/console-browserify-1.1.0.tgz",
"dependencies": {
"date-now": {
"version": "0.1.4",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/date-now/-/date-now-0.1.4.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/date-now/-/date-now-0.1.4.tgz"
}
}
},
"constants-browserify": {
"version": "0.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/constants-browserify/-/constants-browserify-0.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/constants-browserify/-/constants-browserify-0.0.1.tgz"
},
"crypto-browserify": {
"version": "3.2.8",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/crypto-browserify/-/crypto-browserify-3.2.8.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/crypto-browserify/-/crypto-browserify-3.2.8.tgz",
"dependencies": {
"pbkdf2-compat": {
"version": "2.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/pbkdf2-compat/-/pbkdf2-compat-2.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/pbkdf2-compat/-/pbkdf2-compat-2.0.1.tgz"
},
"ripemd160": {
"version": "0.2.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/ripemd160/-/ripemd160-0.2.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/ripemd160/-/ripemd160-0.2.0.tgz"
},
"sha.js": {
"version": "2.2.6",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/sha.js/-/sha.js-2.2.6.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/sha.js/-/sha.js-2.2.6.tgz"
}
}
},
"domain-browser": {
"version": "1.1.4",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/domain-browser/-/domain-browser-1.1.4.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/domain-browser/-/domain-browser-1.1.4.tgz"
},
"events": {
"version": "1.1.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/events/-/events-1.1.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/events/-/events-1.1.0.tgz"
},
"http-browserify": {
"version": "1.7.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/http-browserify/-/http-browserify-1.7.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/http-browserify/-/http-browserify-1.7.0.tgz",
"dependencies": {
"Base64": {
"version": "0.2.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/Base64/-/Base64-0.2.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/Base64/-/Base64-0.2.1.tgz"
},
"inherits": {
"version": "2.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"https-browserify": {
"version": "0.0.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/https-browserify/-/https-browserify-0.0.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/https-browserify/-/https-browserify-0.0.0.tgz"
},
"os-browserify": {
"version": "0.1.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/os-browserify/-/os-browserify-0.1.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/os-browserify/-/os-browserify-0.1.2.tgz"
},
"path-browserify": {
"version": "0.0.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/path-browserify/-/path-browserify-0.0.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/path-browserify/-/path-browserify-0.0.0.tgz"
},
"process": {
"version": "0.11.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/process/-/process-0.11.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/process/-/process-0.11.2.tgz"
},
"punycode": {
"version": "1.3.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/punycode/-/punycode-1.3.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/punycode/-/punycode-1.3.2.tgz"
},
"querystring-es3": {
"version": "0.2.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/querystring-es3/-/querystring-es3-0.2.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/querystring-es3/-/querystring-es3-0.2.1.tgz"
},
"readable-stream": {
"version": "1.1.13",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-1.1.13.tgz",
"dependencies": {
"core-util-is": {
"version": "1.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.1.tgz"
},
"isarray": {
"version": "0.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz"
},
"inherits": {
"version": "2.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"stream-browserify": {
"version": "1.0.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/stream-browserify/-/stream-browserify-1.0.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/stream-browserify/-/stream-browserify-1.0.0.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"string_decoder": {
"version": "0.10.31",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-0.10.31.tgz"
},
"timers-browserify": {
"version": "1.4.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/timers-browserify/-/timers-browserify-1.4.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/timers-browserify/-/timers-browserify-1.4.1.tgz"
},
"tty-browserify": {
"version": "0.0.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/tty-browserify/-/tty-browserify-0.0.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/tty-browserify/-/tty-browserify-0.0.0.tgz"
},
"url": {
"version": "0.10.3",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/url/-/url-0.10.3.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/url/-/url-0.10.3.tgz",
"dependencies": {
"querystring": {
"version": "0.2.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/querystring/-/querystring-0.2.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/querystring/-/querystring-0.2.0.tgz"
}
}
},
"util": {
"version": "0.10.3",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/util/-/util-0.10.3.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/util/-/util-0.10.3.tgz",
"dependencies": {
"inherits": {
"version": "2.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.1.tgz"
}
}
},
"vm-browserify": {
"version": "0.0.4",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/vm-browserify/-/vm-browserify-0.0.4.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/vm-browserify/-/vm-browserify-0.0.4.tgz",
"dependencies": {
"indexof": {
"version": "0.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz"
}
}
}
}
},
"optimist": {
"version": "0.6.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
"dependencies": {
"wordwrap": {
"version": "0.0.3",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.3.tgz"
},
"minimist": {
"version": "0.0.10",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz"
}
}
},
"supports-color": {
"version": "3.1.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/supports-color/-/supports-color-3.1.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-3.1.2.tgz",
"dependencies": {
"has-flag": {
"version": "1.0.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/has-flag/-/has-flag-1.0.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-1.0.0.tgz"
}
}
},
"tapable": {
"version": "0.1.9",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/tapable/-/tapable-0.1.9.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/tapable/-/tapable-0.1.9.tgz"
},
"uglify-js": {
"version": "2.6.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.6.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.6.1.tgz",
"dependencies": {
"async": {
"version": "0.2.10",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz"
},
"source-map": {
"version": "0.5.3",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.3.tgz"
},
"uglify-to-browserify": {
"version": "1.0.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz"
},
"yargs": {
"version": "3.10.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/yargs/-/yargs-3.10.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/yargs/-/yargs-3.10.0.tgz",
"dependencies": {
"camelcase": {
"version": "1.2.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
},
"cliui": {
"version": "2.1.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/cliui/-/cliui-2.1.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/cliui/-/cliui-2.1.0.tgz",
"dependencies": {
"center-align": {
"version": "0.1.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/center-align/-/center-align-0.1.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/center-align/-/center-align-0.1.2.tgz",
"dependencies": {
"align-text": {
"version": "0.1.3",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/align-text/-/align-text-0.1.3.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/align-text/-/align-text-0.1.3.tgz",
"dependencies": {
"kind-of": {
"version": "2.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/kind-of/-/kind-of-2.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-2.0.1.tgz",
"dependencies": {
"is-buffer": {
"version": "1.1.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.0.tgz"
}
}
},
"longest": {
"version": "1.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/longest/-/longest-1.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/longest/-/longest-1.0.1.tgz"
},
"repeat-string": {
"version": "1.5.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.5.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.5.2.tgz"
}
}
},
"lazy-cache": {
"version": "0.2.4",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/lazy-cache/-/lazy-cache-0.2.4.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/lazy-cache/-/lazy-cache-0.2.4.tgz"
}
}
},
"right-align": {
"version": "0.1.3",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/right-align/-/right-align-0.1.3.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/right-align/-/right-align-0.1.3.tgz",
"dependencies": {
"align-text": {
"version": "0.1.3",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/align-text/-/align-text-0.1.3.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/align-text/-/align-text-0.1.3.tgz",
"dependencies": {
"kind-of": {
"version": "2.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/kind-of/-/kind-of-2.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-2.0.1.tgz",
"dependencies": {
"is-buffer": {
"version": "1.1.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.0.tgz"
}
}
},
"longest": {
"version": "1.0.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/longest/-/longest-1.0.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/longest/-/longest-1.0.1.tgz"
},
"repeat-string": {
"version": "1.5.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.5.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.5.2.tgz"
}
}
}
}
},
"wordwrap": {
"version": "0.0.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz"
}
}
},
"decamelize": {
"version": "1.1.1",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/decamelize/-/decamelize-1.1.1.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/decamelize/-/decamelize-1.1.1.tgz"
},
"window-size": {
"version": "0.1.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/window-size/-/window-size-0.1.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/window-size/-/window-size-0.1.0.tgz"
}
}
}
}
},
"watchpack": {
"version": "0.2.9",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/watchpack/-/watchpack-0.2.9.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/watchpack/-/watchpack-0.2.9.tgz",
"dependencies": {
"async": {
"version": "0.9.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/async/-/async-0.9.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/async/-/async-0.9.2.tgz"
},
"graceful-fs": {
"version": "4.1.2",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.2.tgz"
}
}
},
"webpack-core": {
"version": "0.6.8",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/webpack-core/-/webpack-core-0.6.8.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/webpack-core/-/webpack-core-0.6.8.tgz",
"dependencies": {
"source-map": {
"version": "0.4.4",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz",
"dependencies": {
"amdefine": {
"version": "1.0.0",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/amdefine/-/amdefine-1.0.0.tgz"
}
}
},
"source-list-map": {
"version": "0.1.5",
chore(bundles): add source maps to umd dev bundles Source maps are in-lined to follow the same conventions as for non-bundled files. Closes #5511
2015-11-30 08:08:22 -05:00
"from": "https://registry.npmjs.org/source-list-map/-/source-list-map-0.1.5.tgz",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"resolved": "https://registry.npmjs.org/source-list-map/-/source-list-map-0.1.5.tgz"
}
}
}
}
},
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"which": {
"version": "1.2.0",
"from": "https://registry.npmjs.org/which/-/which-1.2.0.tgz",
"resolved": "https://registry.npmjs.org/which/-/which-1.2.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"dependencies": {
build(npm): cleanup + update npm dependencies + reshrinkwrap In the previous commit I removed unused dependencies from package.json, but in order for the change to take effect I needed to update npm shrinkwrap as well. That got complicated because of how npm dedupes packages. Long story short, to clean up the mess I did the following: - deleted npm-shrinkwrap.json and npm-shrinkwrap.clean.json - ran: npm install - ran: npm shrinkwrap --dev && ./tools/npm/clean-npm-shrinkwrap This means that our npm-shrinkwrap now correctly reflects the constraints in package.json, but it also means that some packages got updated (within the version constrain specified in package.json). Some dependencies were intentionally not updated. e.g. mudge due to #5022
2015-10-29 20:58:42 -04:00
"is-absolute": {
"version": "0.1.7",
"from": "https://registry.npmjs.org/is-absolute/-/is-absolute-0.1.7.tgz",
"resolved": "https://registry.npmjs.org/is-absolute/-/is-absolute-0.1.7.tgz",
"dependencies": {
"is-relative": {
"version": "0.1.3",
"from": "https://registry.npmjs.org/is-relative/-/is-relative-0.1.3.tgz",
"resolved": "https://registry.npmjs.org/is-relative/-/is-relative-0.1.3.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
},
"yargs": {
"version": "2.3.0",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/yargs/-/yargs-2.3.0.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/yargs/-/yargs-2.3.0.tgz",
"dependencies": {
"wordwrap": {
"version": "0.0.2",
chore(package.json): bump zone to 0.4.4
2015-05-07 17:32:01 -04:00
"from": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz",
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz"
}
}
},
"zone.js": {
chore(zone.js): update to 0.5.8 fixes #4531
2015-10-06 13:41:46 -04:00
"version": "0.5.8",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"from": "https://registry.npmjs.org/zone.js/-/zone.js-0.5.8.tgz",
chore(zone.js): update to 0.5.8 fixes #4531
2015-10-06 13:41:46 -04:00
"resolved": "https://registry.npmjs.org/zone.js/-/zone.js-0.5.8.tgz",
build(npm): resolve shrinkwrap conflicts after rebase
2015-09-26 00:42:41 -04:00
"dependencies": {
"es6-promise": {
"version": "3.0.2",
chore(ci): update Protractor version, remove custom waits The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes #3829
2015-10-07 00:00:26 -04:00
"from": "https://registry.npmjs.org/es6-promise/-/es6-promise-3.0.2.tgz",
build(npm): resolve shrinkwrap conflicts after rebase
2015-09-26 00:42:41 -04:00
"resolved": "https://registry.npmjs.org/es6-promise/-/es6-promise-3.0.2.tgz"
}
}
chore(npm): add shrinkwrap to our project
2015-04-15 23:36:02 -04:00
}
}
}