strepsirrhini/libreoffice-online
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
libreoffice-online/loleaflet/npm-shrinkwrap.json

2946 lines
109 KiB
JSON
Raw Normal View History

loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
{
loleaflet: Update npm-shrinkwrap.json with updated module name s/leaflet/loleaflet/ in 2b7bd99fcd314834d503920307213b8f5f24c5dc
2016-08-11 05:23:31 -05:00
"name": "loleaflet",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"version": "0.8.0-dev",
"dependencies": {
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"autolinker": {
"version": "1.4.3",
"from": "autolinker@latest",
"resolved": "./node_shrinkwrap/autolinker-1.4.3.tgz",
"dev": true
},
loleaflet: Browserify admin, more modularization, npm-isation Use browserify for admin console scripts too. Modularize needed files such as l10n strings for console. Use npm for managing bootstrap as dependency of admin console.
2016-08-09 09:26:05 -05:00
"bootstrap": {
"version": "3.3.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/bootstrap-3.3.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/bootstrap-3.3.6.tgz",
"dev": true
loleaflet: Browserify admin, more modularization, npm-isation Use browserify for admin console scripts too. Modularize needed files such as l10n strings for console. Use npm for managing bootstrap as dependency of admin console.
2016-08-09 09:26:05 -05:00
},
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"browserify": {
"version": "13.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-13.1.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browserify-13.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"assert": {
"version": "1.3.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/assert-1.3.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/assert-1.3.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"browser-pack": {
"version": "6.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browser-pack-6.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browser-pack-6.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"combine-source-map": {
"version": "0.7.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/combine-source-map-0.7.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/combine-source-map-0.7.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"convert-source-map": {
"version": "1.1.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/convert-source-map-1.1.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/convert-source-map-1.1.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"inline-source-map": {
"version": "0.6.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inline-source-map-0.6.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/inline-source-map-0.6.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"lodash.memoize": {
"version": "3.0.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lodash.memoize-3.0.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/lodash.memoize-3.0.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"source-map": {
"version": "0.5.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/source-map-0.5.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/source-map-0.5.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"umd": {
"version": "3.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/umd-3.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/umd-3.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"browser-resolve": {
"version": "1.11.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browser-resolve-1.11.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/browser-resolve-1.11.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"browserify-zlib": {
"version": "0.1.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-zlib-0.1.4.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browserify-zlib-0.1.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"pako": {
"version": "0.2.9",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/pako-0.2.9.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/pako-0.2.9.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"buffer": {
"version": "4.7.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/buffer-4.7.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/buffer-4.7.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"base64-js": {
"version": "1.1.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/base64-js-1.1.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/base64-js-1.1.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"ieee754": {
"version": "1.1.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ieee754-1.1.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ieee754-1.1.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"isarray": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/isarray-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/isarray-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"concat-stream": {
"version": "1.5.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/concat-stream-1.5.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/concat-stream-1.5.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"readable-stream": {
"version": "2.0.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/readable-stream-2.0.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/readable-stream-2.0.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"core-util-is": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/core-util-is-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/core-util-is-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"isarray": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/isarray-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/isarray-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"process-nextick-args": {
"version": "1.0.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/process-nextick-args-1.0.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/process-nextick-args-1.0.7.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"util-deprecate": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/util-deprecate-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/util-deprecate-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
},
"typedarray": {
"version": "0.0.6",
"from": "node_shrinkwrap/typedarray-0.0.6.tgz",
"resolved": "./node_shrinkwrap/typedarray-0.0.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"console-browserify": {
"version": "1.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/console-browserify-1.1.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/console-browserify-1.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"date-now": {
"version": "0.1.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/date-now-0.1.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/date-now-0.1.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"constants-browserify": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/constants-browserify-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/constants-browserify-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"crypto-browserify": {
"version": "3.11.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/crypto-browserify-3.11.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/crypto-browserify-3.11.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"browserify-cipher": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-cipher-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browserify-cipher-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"browserify-aes": {
"version": "1.0.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-aes-1.0.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browserify-aes-1.0.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"buffer-xor": {
"version": "1.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/buffer-xor-1.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/buffer-xor-1.0.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"cipher-base": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/cipher-base-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/cipher-base-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"browserify-des": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-des-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browserify-des-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"cipher-base": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/cipher-base-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/cipher-base-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"des.js": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/des.js-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/des.js-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"minimalistic-assert": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimalistic-assert-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/minimalistic-assert-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"evp_bytestokey": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/evp_bytestokey-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/evp_bytestokey-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"browserify-sign": {
"version": "4.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-sign-4.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browserify-sign-4.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"bn.js": {
"version": "4.11.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/bn.js-4.11.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/bn.js-4.11.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"browserify-rsa": {
"version": "4.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-rsa-4.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/browserify-rsa-4.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"elliptic": {
"version": "6.3.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/elliptic-6.3.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/elliptic-6.3.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"brorand": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/brorand-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/brorand-1.0.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"hash.js": {
"version": "1.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/hash.js-1.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/hash.js-1.0.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"parse-asn1": {
"version": "5.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/parse-asn1-5.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/parse-asn1-5.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"asn1.js": {
"version": "4.8.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/asn1.js-4.8.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/asn1.js-4.8.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"minimalistic-assert": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimalistic-assert-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/minimalistic-assert-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"browserify-aes": {
"version": "1.0.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-aes-1.0.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browserify-aes-1.0.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"buffer-xor": {
"version": "1.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/buffer-xor-1.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/buffer-xor-1.0.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"cipher-base": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/cipher-base-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/cipher-base-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"evp_bytestokey": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/evp_bytestokey-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/evp_bytestokey-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"create-ecdh": {
"version": "4.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/create-ecdh-4.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/create-ecdh-4.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"bn.js": {
"version": "4.11.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/bn.js-4.11.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/bn.js-4.11.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"elliptic": {
"version": "6.3.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/elliptic-6.3.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/elliptic-6.3.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"brorand": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/brorand-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/brorand-1.0.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"hash.js": {
"version": "1.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/hash.js-1.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/hash.js-1.0.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"create-hash": {
"version": "1.1.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/create-hash-1.1.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/create-hash-1.1.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"cipher-base": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/cipher-base-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/cipher-base-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"ripemd160": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ripemd160-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ripemd160-1.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"sha.js": {
"version": "2.4.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/sha.js-2.4.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/sha.js-2.4.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"create-hmac": {
"version": "1.1.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/create-hmac-1.1.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/create-hmac-1.1.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"diffie-hellman": {
"version": "5.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/diffie-hellman-5.0.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/diffie-hellman-5.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"bn.js": {
"version": "4.11.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/bn.js-4.11.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/bn.js-4.11.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"miller-rabin": {
"version": "4.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/miller-rabin-4.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/miller-rabin-4.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"brorand": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/brorand-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/brorand-1.0.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"pbkdf2": {
"version": "3.0.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/pbkdf2-3.0.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/pbkdf2-3.0.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"public-encrypt": {
"version": "4.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/public-encrypt-4.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/public-encrypt-4.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"bn.js": {
"version": "4.11.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/bn.js-4.11.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/bn.js-4.11.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"browserify-rsa": {
"version": "4.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-rsa-4.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/browserify-rsa-4.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"parse-asn1": {
"version": "5.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/parse-asn1-5.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/parse-asn1-5.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"asn1.js": {
"version": "4.8.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/asn1.js-4.8.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/asn1.js-4.8.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"minimalistic-assert": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimalistic-assert-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/minimalistic-assert-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"browserify-aes": {
"version": "1.0.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-aes-1.0.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browserify-aes-1.0.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"buffer-xor": {
"version": "1.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/buffer-xor-1.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/buffer-xor-1.0.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"cipher-base": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/cipher-base-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/cipher-base-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"evp_bytestokey": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/evp_bytestokey-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/evp_bytestokey-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"randombytes": {
"version": "2.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/randombytes-2.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/randombytes-2.0.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"defined": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/defined-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/defined-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"deps-sort": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/deps-sort-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/deps-sort-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"domain-browser": {
"version": "1.1.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/domain-browser-1.1.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/domain-browser-1.1.7.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"duplexer2": {
"version": "0.1.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/duplexer2-0.1.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/duplexer2-0.1.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"events": {
"version": "1.1.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/events-1.1.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/events-1.1.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"glob": {
"version": "5.0.15",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/glob-5.0.15.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/glob-5.0.15.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"inflight": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inflight-1.0.5.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/inflight-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"wrappy": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wrappy-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wrappy-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"minimatch": {
"version": "3.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimatch-3.0.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/minimatch-3.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"brace-expansion": {
"version": "1.1.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"balanced-match": {
"version": "0.4.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/balanced-match-0.4.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/balanced-match-0.4.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"concat-map": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/concat-map-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/concat-map-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"once": {
"version": "1.3.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/once-1.3.3.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/once-1.3.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"wrappy": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wrappy-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wrappy-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"path-is-absolute": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/path-is-absolute-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/path-is-absolute-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"has": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/has-1.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/has-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"function-bind": {
"version": "1.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/function-bind-1.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/function-bind-1.1.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"htmlescape": {
"version": "1.1.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/htmlescape-1.1.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/htmlescape-1.1.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"https-browserify": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/https-browserify-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/https-browserify-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"inherits": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inherits-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/inherits-2.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"insert-module-globals": {
"version": "7.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/insert-module-globals-7.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/insert-module-globals-7.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"combine-source-map": {
"version": "0.7.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/combine-source-map-0.7.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/combine-source-map-0.7.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"convert-source-map": {
"version": "1.1.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/convert-source-map-1.1.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/convert-source-map-1.1.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"inline-source-map": {
"version": "0.6.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inline-source-map-0.6.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/inline-source-map-0.6.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"lodash.memoize": {
"version": "3.0.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lodash.memoize-3.0.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/lodash.memoize-3.0.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"source-map": {
"version": "0.5.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/source-map-0.5.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/source-map-0.5.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"is-buffer": {
"version": "1.1.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-buffer-1.1.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/is-buffer-1.1.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"lexical-scope": {
"version": "1.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lexical-scope-1.2.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/lexical-scope-1.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"astw": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/astw-2.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/astw-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"acorn": {
"version": "1.2.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/acorn-1.2.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/acorn-1.2.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
}
}
},
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"JSONStream": {
"version": "1.1.4",
"from": "node_shrinkwrap/JSONStream-1.1.4.tgz",
"resolved": "./node_shrinkwrap/JSONStream-1.1.4.tgz",
"dev": true,
"dependencies": {
"jsonparse": {
"version": "1.2.0",
"from": "node_shrinkwrap/jsonparse-1.2.0.tgz",
"resolved": "./node_shrinkwrap/jsonparse-1.2.0.tgz",
"dev": true
},
"through": {
"version": "2.3.8",
"from": "node_shrinkwrap/through-2.3.8.tgz",
"resolved": "./node_shrinkwrap/through-2.3.8.tgz",
"dev": true
}
}
},
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"labeled-stream-splicer": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/labeled-stream-splicer-2.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/labeled-stream-splicer-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"isarray": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/isarray-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/isarray-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"stream-splicer": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/stream-splicer-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/stream-splicer-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"module-deps": {
"version": "4.0.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/module-deps-4.0.7.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/module-deps-4.0.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"detective": {
"version": "4.3.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/detective-4.3.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/detective-4.3.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"acorn": {
"version": "1.2.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/acorn-1.2.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/acorn-1.2.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"stream-combiner2": {
"version": "1.1.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/stream-combiner2-1.1.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/stream-combiner2-1.1.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"os-browserify": {
"version": "0.1.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/os-browserify-0.1.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/os-browserify-0.1.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"parents": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/parents-1.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/parents-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"path-platform": {
"version": "0.11.15",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/path-platform-0.11.15.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/path-platform-0.11.15.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"path-browserify": {
"version": "0.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/path-browserify-0.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/path-browserify-0.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"process": {
"version": "0.11.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/process-0.11.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/process-0.11.7.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"punycode": {
"version": "1.4.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/punycode-1.4.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/punycode-1.4.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"querystring-es3": {
"version": "0.2.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/querystring-es3-0.2.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/querystring-es3-0.2.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"read-only-stream": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/read-only-stream-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/read-only-stream-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"readable-stream": {
"version": "2.1.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/readable-stream-2.1.4.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/readable-stream-2.1.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"buffer-shims": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/buffer-shims-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/buffer-shims-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"core-util-is": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/core-util-is-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/core-util-is-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"isarray": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/isarray-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/isarray-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"process-nextick-args": {
"version": "1.0.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/process-nextick-args-1.0.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/process-nextick-args-1.0.7.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"util-deprecate": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/util-deprecate-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/util-deprecate-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"resolve": {
"version": "1.1.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/resolve-1.1.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/resolve-1.1.7.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"shasum": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/shasum-1.0.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/shasum-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"json-stable-stringify": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/json-stable-stringify-0.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/json-stable-stringify-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"jsonify": {
"version": "0.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/jsonify-0.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/jsonify-0.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"sha.js": {
"version": "2.4.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/sha.js-2.4.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/sha.js-2.4.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"shell-quote": {
"version": "1.6.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/shell-quote-1.6.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/shell-quote-1.6.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"array-filter": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/array-filter-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/array-filter-0.0.1.tgz",
"dev": true
},
"array-map": {
"version": "0.0.0",
"from": "node_shrinkwrap/array-map-0.0.0.tgz",
"resolved": "./node_shrinkwrap/array-map-0.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"array-reduce": {
"version": "0.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/array-reduce-0.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/array-reduce-0.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"jsonify": {
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"version": "0.0.0",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"from": "node_shrinkwrap/jsonify-0.0.0.tgz",
"resolved": "./node_shrinkwrap/jsonify-0.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"stream-browserify": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/stream-browserify-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/stream-browserify-2.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"stream-http": {
"version": "2.3.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/stream-http-2.3.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/stream-http-2.3.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"builtin-status-codes": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/builtin-status-codes-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/builtin-status-codes-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"to-arraybuffer": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/to-arraybuffer-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/to-arraybuffer-1.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"string_decoder": {
"version": "0.10.31",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/string_decoder-0.10.31.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/string_decoder-0.10.31.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"subarg": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/subarg-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/subarg-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"minimist": {
"version": "1.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimist-1.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/minimist-1.2.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"syntax-error": {
"version": "1.1.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/syntax-error-1.1.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/syntax-error-1.1.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"acorn": {
"version": "2.7.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/acorn-2.7.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/acorn-2.7.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"through2": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/through2-2.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/through2-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"readable-stream": {
"version": "2.0.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/readable-stream-2.0.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/readable-stream-2.0.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"core-util-is": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/core-util-is-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/core-util-is-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"isarray": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/isarray-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/isarray-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"process-nextick-args": {
"version": "1.0.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/process-nextick-args-1.0.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/process-nextick-args-1.0.7.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"util-deprecate": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/util-deprecate-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/util-deprecate-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"timers-browserify": {
"version": "1.4.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/timers-browserify-1.4.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/timers-browserify-1.4.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"tty-browserify": {
"version": "0.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/tty-browserify-0.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/tty-browserify-0.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"url": {
"version": "0.11.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/url-0.11.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/url-0.11.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"punycode": {
"version": "1.3.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/punycode-1.3.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/punycode-1.3.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"querystring": {
"version": "0.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/querystring-0.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/querystring-0.2.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"util": {
"version": "0.10.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/util-0.10.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/util-0.10.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"vm-browserify": {
"version": "0.0.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/vm-browserify-0.0.4.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/vm-browserify-0.0.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"indexof": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/indexof-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/indexof-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"xtend": {
"version": "4.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/xtend-4.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/xtend-4.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"browserify-css": {
"version": "0.9.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/browserify-css-0.9.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/browserify-css-0.9.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"clean-css": {
"version": "2.2.23",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/clean-css-2.2.23.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/clean-css-2.2.23.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"commander": {
"version": "2.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/commander-2.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/commander-2.2.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"concat-stream": {
"version": "1.4.10",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/concat-stream-1.4.10.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/concat-stream-1.4.10.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"inherits": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inherits-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/inherits-2.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"readable-stream": {
"version": "1.1.14",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/readable-stream-1.1.14.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/readable-stream-1.1.14.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"core-util-is": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/core-util-is-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/core-util-is-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"isarray": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/isarray-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/isarray-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"string_decoder": {
"version": "0.10.31",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/string_decoder-0.10.31.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/string_decoder-0.10.31.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
},
"typedarray": {
"version": "0.0.6",
"from": "node_shrinkwrap/typedarray-0.0.6.tgz",
"resolved": "./node_shrinkwrap/typedarray-0.0.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"css": {
"version": "1.6.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/css-1.6.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/css-1.6.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"css-parse": {
"version": "1.7.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/css-parse-1.7.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/css-parse-1.7.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"css-stringify": {
"version": "1.4.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/css-stringify-1.4.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/css-stringify-1.4.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"source-map": {
"version": "0.1.43",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/source-map-0.1.43.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/source-map-0.1.43.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"amdefine": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/amdefine-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/amdefine-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
}
}
},
"find-node-modules": {
"version": "1.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/find-node-modules-1.0.3.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/find-node-modules-1.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"findup-sync": {
"version": "0.2.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/findup-sync-0.2.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/findup-sync-0.2.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"glob": {
"version": "4.3.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/glob-4.3.5.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/glob-4.3.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"inflight": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inflight-1.0.5.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/inflight-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"wrappy": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wrappy-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wrappy-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"inherits": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inherits-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/inherits-2.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"minimatch": {
"version": "2.0.10",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimatch-2.0.10.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/minimatch-2.0.10.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"brace-expansion": {
"version": "1.1.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"balanced-match": {
"version": "0.4.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/balanced-match-0.4.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/balanced-match-0.4.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"concat-map": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/concat-map-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/concat-map-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"once": {
"version": "1.3.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/once-1.3.3.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/once-1.3.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"wrappy": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wrappy-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wrappy-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
}
}
},
"merge": {
"version": "1.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/merge-1.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/merge-1.2.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"lodash": {
"version": "3.6.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lodash-3.6.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/lodash-3.6.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"through2": {
"version": "0.6.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/through2-0.6.5.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/through2-0.6.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"readable-stream": {
"version": "1.0.34",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/readable-stream-1.0.34.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/readable-stream-1.0.34.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"core-util-is": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/core-util-is-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/core-util-is-1.0.2.tgz",
"dev": true
},
"inherits": {
"version": "2.0.1",
"from": "node_shrinkwrap/inherits-2.0.1.tgz",
"resolved": "./node_shrinkwrap/inherits-2.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"isarray": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/isarray-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/isarray-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"string_decoder": {
"version": "0.10.31",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/string_decoder-0.10.31.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/string_decoder-0.10.31.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"xtend": {
"version": "4.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/xtend-4.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/xtend-4.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
loleaflet: npm-sify d3.js Don't use external CDN for this library, rather 'require()' it from our local npm modules.
2016-08-09 09:43:00 -05:00
"d3": {
"version": "3.5.17",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/d3-3.5.17.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/d3-3.5.17.tgz",
"dev": true
loleaflet: npm-sify d3.js Don't use external CDN for this library, rather 'require()' it from our local npm modules.
2016-08-09 09:43:00 -05:00
},
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"eslint": {
"version": "2.13.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/eslint-2.13.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/eslint-2.13.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"chalk": {
"version": "1.1.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/chalk-1.1.3.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/chalk-1.1.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"ansi-styles": {
"version": "2.2.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ansi-styles-2.2.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ansi-styles-2.2.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"escape-string-regexp": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/escape-string-regexp-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/escape-string-regexp-1.0.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"has-ansi": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/has-ansi-2.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/has-ansi-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ansi-regex-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ansi-regex-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"strip-ansi": {
"version": "3.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/strip-ansi-3.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/strip-ansi-3.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ansi-regex-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ansi-regex-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"supports-color": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/supports-color-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/supports-color-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"concat-stream": {
"version": "1.5.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/concat-stream-1.5.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/concat-stream-1.5.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"inherits": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inherits-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/inherits-2.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"readable-stream": {
"version": "2.0.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/readable-stream-2.0.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/readable-stream-2.0.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"core-util-is": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/core-util-is-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/core-util-is-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"isarray": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/isarray-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/isarray-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"process-nextick-args": {
"version": "1.0.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/process-nextick-args-1.0.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/process-nextick-args-1.0.7.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"string_decoder": {
"version": "0.10.31",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/string_decoder-0.10.31.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/string_decoder-0.10.31.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"util-deprecate": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/util-deprecate-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/util-deprecate-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
},
"typedarray": {
"version": "0.0.6",
"from": "node_shrinkwrap/typedarray-0.0.6.tgz",
"resolved": "./node_shrinkwrap/typedarray-0.0.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"debug": {
"version": "2.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/debug-2.2.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/debug-2.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"ms": {
"version": "0.7.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ms-0.7.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ms-0.7.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"doctrine": {
"version": "1.2.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/doctrine-1.2.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/doctrine-1.2.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"esutils": {
"version": "1.1.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/esutils-1.1.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/esutils-1.1.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"isarray": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/isarray-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/isarray-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"es6-map": {
"version": "0.1.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/es6-map-0.1.4.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/es6-map-0.1.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"d": {
"version": "0.1.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/d-0.1.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/d-0.1.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"es5-ext": {
"version": "0.10.12",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/es5-ext-0.10.12.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/es5-ext-0.10.12.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"es6-iterator": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/es6-iterator-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/es6-iterator-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"es6-set": {
"version": "0.1.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/es6-set-0.1.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/es6-set-0.1.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"es6-symbol": {
"version": "3.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/es6-symbol-3.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/es6-symbol-3.1.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"event-emitter": {
"version": "0.3.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/event-emitter-0.3.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/event-emitter-0.3.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"escope": {
"version": "3.6.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/escope-3.6.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/escope-3.6.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"es6-weak-map": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/es6-weak-map-2.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/es6-weak-map-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"d": {
"version": "0.1.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/d-0.1.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/d-0.1.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"es5-ext": {
"version": "0.10.12",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/es5-ext-0.10.12.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/es5-ext-0.10.12.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"es6-iterator": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/es6-iterator-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/es6-iterator-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"es6-symbol": {
"version": "3.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/es6-symbol-3.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/es6-symbol-3.1.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"esrecurse": {
"version": "4.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/esrecurse-4.1.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/esrecurse-4.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"estraverse": {
"version": "4.1.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/estraverse-4.1.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/estraverse-4.1.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"object-assign": {
"version": "4.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/object-assign-4.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/object-assign-4.1.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"espree": {
"version": "3.1.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/espree-3.1.7.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/espree-3.1.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"acorn": {
"version": "3.3.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/acorn-3.3.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/acorn-3.3.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"acorn-jsx": {
"version": "3.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/acorn-jsx-3.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/acorn-jsx-3.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"estraverse": {
"version": "4.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/estraverse-4.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/estraverse-4.2.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"esutils": {
"version": "2.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/esutils-2.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/esutils-2.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"file-entry-cache": {
"version": "1.3.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/file-entry-cache-1.3.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/file-entry-cache-1.3.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"flat-cache": {
"version": "1.2.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/flat-cache-1.2.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/flat-cache-1.2.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"circular-json": {
"version": "0.3.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/circular-json-0.3.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/circular-json-0.3.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"del": {
"version": "2.2.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/del-2.2.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/del-2.2.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"globby": {
"version": "5.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/globby-5.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/globby-5.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"array-union": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/array-union-1.0.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/array-union-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"array-uniq": {
"version": "1.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/array-uniq-1.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/array-uniq-1.0.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"arrify": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/arrify-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/arrify-1.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"is-path-cwd": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-path-cwd-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/is-path-cwd-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"is-path-in-cwd": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-path-in-cwd-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/is-path-in-cwd-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"is-path-inside": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-path-inside-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/is-path-inside-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"pify": {
"version": "2.3.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/pify-2.3.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/pify-2.3.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"pinkie-promise": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/pinkie-promise-2.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/pinkie-promise-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"pinkie": {
"version": "2.0.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/pinkie-2.0.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/pinkie-2.0.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"rimraf": {
"version": "2.5.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/rimraf-2.5.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/rimraf-2.5.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"graceful-fs": {
"version": "4.1.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/graceful-fs-4.1.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/graceful-fs-4.1.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"write": {
"version": "0.2.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/write-0.2.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/write-0.2.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"object-assign": {
"version": "4.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/object-assign-4.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/object-assign-4.1.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"glob": {
"version": "7.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/glob-7.0.5.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/glob-7.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"fs.realpath": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/fs.realpath-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/fs.realpath-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"inflight": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inflight-1.0.5.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/inflight-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"wrappy": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wrappy-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wrappy-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"inherits": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inherits-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/inherits-2.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"minimatch": {
"version": "3.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimatch-3.0.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/minimatch-3.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"brace-expansion": {
"version": "1.1.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"balanced-match": {
"version": "0.4.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/balanced-match-0.4.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/balanced-match-0.4.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"concat-map": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/concat-map-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/concat-map-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"once": {
"version": "1.3.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/once-1.3.3.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/once-1.3.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"wrappy": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wrappy-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wrappy-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"globals": {
"version": "9.9.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/globals-9.9.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/globals-9.9.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"ignore": {
"version": "3.1.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ignore-3.1.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ignore-3.1.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"imurmurhash": {
"version": "0.1.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/imurmurhash-0.1.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/imurmurhash-0.1.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"inquirer": {
"version": "0.12.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inquirer-0.12.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/inquirer-0.12.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"ansi-escapes": {
"version": "1.4.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ansi-escapes-1.4.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ansi-escapes-1.4.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"ansi-regex": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ansi-regex-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ansi-regex-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"cli-cursor": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/cli-cursor-1.0.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/cli-cursor-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"restore-cursor": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/restore-cursor-1.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/restore-cursor-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"exit-hook": {
"version": "1.1.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/exit-hook-1.1.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/exit-hook-1.1.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"onetime": {
"version": "1.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/onetime-1.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/onetime-1.1.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"cli-width": {
"version": "2.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/cli-width-2.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/cli-width-2.1.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"figures": {
"version": "1.7.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/figures-1.7.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/figures-1.7.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"escape-string-regexp": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/escape-string-regexp-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/escape-string-regexp-1.0.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"object-assign": {
"version": "4.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/object-assign-4.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/object-assign-4.1.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"readline2": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/readline2-1.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/readline2-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"code-point-at": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/code-point-at-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/code-point-at-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/number-is-nan-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/number-is-nan-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"is-fullwidth-code-point": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-fullwidth-code-point-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/is-fullwidth-code-point-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/number-is-nan-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/number-is-nan-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"mute-stream": {
"version": "0.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/mute-stream-0.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/mute-stream-0.0.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"run-async": {
"version": "0.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/run-async-0.1.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/run-async-0.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"once": {
"version": "1.3.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/once-1.3.3.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/once-1.3.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"wrappy": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wrappy-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wrappy-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"rx-lite": {
"version": "3.1.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/rx-lite-3.1.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/rx-lite-3.1.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"string-width": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/string-width-1.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/string-width-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"code-point-at": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/code-point-at-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/code-point-at-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/number-is-nan-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/number-is-nan-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"is-fullwidth-code-point": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-fullwidth-code-point-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/is-fullwidth-code-point-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/number-is-nan-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/number-is-nan-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"strip-ansi": {
"version": "3.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/strip-ansi-3.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/strip-ansi-3.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"through": {
"version": "2.3.8",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/through-2.3.8.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/through-2.3.8.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"is-my-json-valid": {
"version": "2.13.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-my-json-valid-2.13.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/is-my-json-valid-2.13.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"generate-function": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/generate-function-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/generate-function-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"generate-object-property": {
"version": "1.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/generate-object-property-1.2.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/generate-object-property-1.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"is-property": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-property-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/is-property-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"jsonpointer": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/jsonpointer-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/jsonpointer-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"xtend": {
"version": "4.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/xtend-4.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/xtend-4.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"is-resolvable": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-resolvable-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/is-resolvable-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"tryit": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/tryit-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/tryit-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"js-yaml": {
"version": "3.6.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/js-yaml-3.6.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/js-yaml-3.6.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"argparse": {
"version": "1.0.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/argparse-1.0.7.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/argparse-1.0.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"sprintf-js": {
"version": "1.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/sprintf-js-1.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/sprintf-js-1.0.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"esprima": {
"version": "2.7.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/esprima-2.7.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/esprima-2.7.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"json-stable-stringify": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/json-stable-stringify-1.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/json-stable-stringify-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"jsonify": {
"version": "0.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/jsonify-0.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/jsonify-0.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"levn": {
"version": "0.3.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/levn-0.3.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/levn-0.3.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"prelude-ls": {
"version": "1.1.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/prelude-ls-1.1.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/prelude-ls-1.1.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"type-check": {
"version": "0.3.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/type-check-0.3.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/type-check-0.3.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"lodash": {
"version": "4.14.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lodash-4.14.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/lodash-4.14.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"mkdirp": {
"version": "0.5.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/mkdirp-0.5.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/mkdirp-0.5.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"minimist": {
"version": "0.0.8",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimist-0.0.8.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/minimist-0.0.8.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"optionator": {
"version": "0.8.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/optionator-0.8.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/optionator-0.8.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"deep-is": {
"version": "0.1.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/deep-is-0.1.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/deep-is-0.1.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"fast-levenshtein": {
"version": "1.1.4",
"from": "node_shrinkwrap/fast-levenshtein-1.1.4.tgz",
"resolved": "./node_shrinkwrap/fast-levenshtein-1.1.4.tgz",
"dev": true
},
"prelude-ls": {
"version": "1.1.2",
"from": "node_shrinkwrap/prelude-ls-1.1.2.tgz",
"resolved": "./node_shrinkwrap/prelude-ls-1.1.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"type-check": {
"version": "0.3.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/type-check-0.3.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/type-check-0.3.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"wordwrap": {
"version": "1.0.0",
"from": "node_shrinkwrap/wordwrap-1.0.0.tgz",
"resolved": "./node_shrinkwrap/wordwrap-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"path-is-absolute": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/path-is-absolute-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/path-is-absolute-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"path-is-inside": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/path-is-inside-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/path-is-inside-1.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"pluralize": {
"version": "1.2.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/pluralize-1.2.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/pluralize-1.2.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"progress": {
"version": "1.1.8",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/progress-1.1.8.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/progress-1.1.8.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"require-uncached": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/require-uncached-1.0.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/require-uncached-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"caller-path": {
"version": "0.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/caller-path-0.1.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/caller-path-0.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"callsites": {
"version": "0.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/callsites-0.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/callsites-0.2.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"resolve-from": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/resolve-from-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/resolve-from-1.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"shelljs": {
"version": "0.6.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/shelljs-0.6.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/shelljs-0.6.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"strip-json-comments": {
"version": "1.0.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/strip-json-comments-1.0.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/strip-json-comments-1.0.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"table": {
"version": "3.7.8",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/table-3.7.8.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/table-3.7.8.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"bluebird": {
"version": "3.4.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/bluebird-3.4.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/bluebird-3.4.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"slice-ansi": {
"version": "0.0.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/slice-ansi-0.0.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/slice-ansi-0.0.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"string-width": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/string-width-1.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/string-width-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"code-point-at": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/code-point-at-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/code-point-at-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/number-is-nan-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/number-is-nan-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"is-fullwidth-code-point": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/is-fullwidth-code-point-1.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/is-fullwidth-code-point-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"number-is-nan": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/number-is-nan-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/number-is-nan-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"strip-ansi": {
"version": "3.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/strip-ansi-3.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/strip-ansi-3.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ansi-regex-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ansi-regex-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"tv4": {
"version": "1.2.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/tv4-1.2.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/tv4-1.2.7.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"xregexp": {
"version": "3.1.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/xregexp-3.1.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/xregexp-3.1.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"text-table": {
"version": "0.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/text-table-0.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/text-table-0.2.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"user-home": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/user-home-2.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/user-home-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"os-homedir": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/os-homedir-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/os-homedir-1.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"evol-colorpicker": {
"version": "3.2.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/evol-colorpicker-3.2.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/evol-colorpicker-3.2.6.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
loleaflet: Add exorcist to dependency tree This is required for separating source maps from our bundles.
2016-08-11 05:57:21 -05:00
"exorcist": {
"version": "0.4.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/exorcist-0.4.0.tgz",
loleaflet: Add exorcist to dependency tree This is required for separating source maps from our bundles.
2016-08-11 05:57:21 -05:00
"resolved": "./node_shrinkwrap/exorcist-0.4.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Add exorcist to dependency tree This is required for separating source maps from our bundles.
2016-08-11 05:57:21 -05:00
"dependencies": {
"minimist": {
"version": "0.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimist-0.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/minimist-0.0.5.tgz",
"dev": true
loleaflet: Add exorcist to dependency tree This is required for separating source maps from our bundles.
2016-08-11 05:57:21 -05:00
},
"mold-source-map": {
"version": "0.4.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/mold-source-map-0.4.0.tgz",
loleaflet: Add exorcist to dependency tree This is required for separating source maps from our bundles.
2016-08-11 05:57:21 -05:00
"resolved": "./node_shrinkwrap/mold-source-map-0.4.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Add exorcist to dependency tree This is required for separating source maps from our bundles.
2016-08-11 05:57:21 -05:00
"dependencies": {
"convert-source-map": {
"version": "1.3.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/convert-source-map-1.3.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/convert-source-map-1.3.0.tgz",
"dev": true
loleaflet: Add exorcist to dependency tree This is required for separating source maps from our bundles.
2016-08-11 05:57:21 -05:00
},
"through": {
"version": "2.2.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/through-2.2.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/through-2.2.7.tgz",
"dev": true
loleaflet: Add exorcist to dependency tree This is required for separating source maps from our bundles.
2016-08-11 05:57:21 -05:00
}
}
},
"nave": {
"version": "0.5.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/nave-0.5.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/nave-0.5.3.tgz",
"dev": true
loleaflet: Add exorcist to dependency tree This is required for separating source maps from our bundles.
2016-08-11 05:57:21 -05:00
}
}
},
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"jake": {
"version": "8.0.12",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/jake-8.0.12.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/jake-8.0.12.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"async": {
"version": "0.9.2",
"from": "node_shrinkwrap/async-0.9.2.tgz",
"resolved": "./node_shrinkwrap/async-0.9.2.tgz",
"dev": true
},
"chalk": {
"version": "0.4.0",
"from": "node_shrinkwrap/chalk-0.4.0.tgz",
"resolved": "./node_shrinkwrap/chalk-0.4.0.tgz",
"dev": true,
"dependencies": {
"ansi-styles": {
"version": "1.0.0",
"from": "node_shrinkwrap/ansi-styles-1.0.0.tgz",
"resolved": "./node_shrinkwrap/ansi-styles-1.0.0.tgz",
"dev": true
},
"has-color": {
"version": "0.1.7",
"from": "node_shrinkwrap/has-color-0.1.7.tgz",
"resolved": "./node_shrinkwrap/has-color-0.1.7.tgz",
"dev": true
},
"strip-ansi": {
"version": "0.1.1",
"from": "node_shrinkwrap/strip-ansi-0.1.1.tgz",
"resolved": "./node_shrinkwrap/strip-ansi-0.1.1.tgz",
"dev": true
}
}
},
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"filelist": {
"version": "0.0.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/filelist-0.0.4.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/filelist-0.0.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"minimatch": {
"version": "0.3.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimatch-0.3.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/minimatch-0.3.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"lru-cache": {
"version": "2.7.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lru-cache-2.7.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/lru-cache-2.7.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"sigmund": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/sigmund-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/sigmund-1.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"utilities": {
"version": "0.0.37",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/utilities-0.0.37.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/utilities-0.0.37.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"minimatch": {
"version": "0.2.14",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimatch-0.2.14.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/minimatch-0.2.14.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"lru-cache": {
"version": "2.7.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lru-cache-2.7.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/lru-cache-2.7.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"sigmund": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/sigmund-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/sigmund-1.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"utilities": {
"version": "1.0.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/utilities-1.0.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/utilities-1.0.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"jquery": {
"version": "2.2.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/jquery-2.2.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/jquery-2.2.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"jquery-contextmenu": {
loleaflet: Bump jquery-contextmenu to 2.2.3 With current version, position of context menu is not set at specified position. 2.2.3 fixes the issue. Also udpate tarballs in node_shrinkwrap and dep. tree in npm-shrinkwrap.json
2016-08-03 02:35:21 -05:00
"version": "2.2.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/jquery-contextmenu-2.2.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/jquery-contextmenu-2.2.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"jquery-ui": {
"version": "1.10.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/jquery-ui-1.10.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/jquery-ui-1.10.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"json-js": {
"version": "1.1.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/json-js-1.1.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/json-js-1.1.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"l10n-for-node": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/l10n-for-node-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/l10n-for-node-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"malihu-custom-scrollbar-plugin": {
"version": "3.1.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/malihu-custom-scrollbar-plugin-3.1.3.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/malihu-custom-scrollbar-plugin-3.1.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"jquery-mousewheel": {
"version": "3.1.13",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/jquery-mousewheel-3.1.13.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/jquery-mousewheel-3.1.13.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"select2": {
"version": "4.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/select2-4.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/select2-4.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"almond": {
"version": "0.3.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/almond-0.3.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/almond-0.3.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"jquery-mousewheel": {
"version": "3.1.13",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/jquery-mousewheel-3.1.13.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/jquery-mousewheel-3.1.13.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"shrinkpack": {
"version": "0.13.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/shrinkpack-0.13.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/shrinkpack-0.13.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"chalk": {
"version": "1.1.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/chalk-1.1.3.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/chalk-1.1.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"ansi-styles": {
"version": "2.2.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ansi-styles-2.2.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ansi-styles-2.2.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"escape-string-regexp": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/escape-string-regexp-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/escape-string-regexp-1.0.5.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"has-ansi": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/has-ansi-2.0.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/has-ansi-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ansi-regex-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ansi-regex-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"strip-ansi": {
"version": "3.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/strip-ansi-3.0.1.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/strip-ansi-3.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"ansi-regex": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/ansi-regex-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/ansi-regex-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"supports-color": {
"version": "2.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/supports-color-2.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/supports-color-2.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"commander": {
"version": "2.9.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/commander-2.9.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/commander-2.9.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"graceful-readlink": {
"version": "1.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/graceful-readlink-1.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/graceful-readlink-1.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"glob": {
"version": "7.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/glob-7.0.5.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/glob-7.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"fs.realpath": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/fs.realpath-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/fs.realpath-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"inflight": {
"version": "1.0.5",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inflight-1.0.5.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/inflight-1.0.5.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"wrappy": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wrappy-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wrappy-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"inherits": {
"version": "2.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/inherits-2.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/inherits-2.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"minimatch": {
"version": "3.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimatch-3.0.2.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/minimatch-3.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"brace-expansion": {
"version": "1.1.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"balanced-match": {
"version": "0.4.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/balanced-match-0.4.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/balanced-match-0.4.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"concat-map": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/concat-map-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/concat-map-0.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"once": {
"version": "1.3.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/once-1.3.3.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/once-1.3.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"wrappy": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wrappy-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wrappy-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"path-is-absolute": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/path-is-absolute-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/path-is-absolute-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"graceful-fs": {
"version": "4.1.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/graceful-fs-4.1.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/graceful-fs-4.1.4.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"lodash.uniq": {
"version": "4.3.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lodash.uniq-4.3.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/lodash.uniq-4.3.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"lodash._baseuniq": {
"version": "4.6.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lodash._baseuniq-4.6.0.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/lodash._baseuniq-4.6.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"lodash._createset": {
"version": "4.0.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lodash._createset-4.0.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/lodash._createset-4.0.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"lodash._root": {
"version": "3.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/lodash._root-3.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/lodash._root-3.0.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
"when": {
"version": "3.7.7",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/when-3.7.7.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/when-3.7.7.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"smartmenus": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/smartmenus-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/smartmenus-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
leaflet: bundle timeago JS module And start using it in DocumentRepair. Change-Id: I8d2b8af4d2e0dcc7cf8082c9d7adbc633df1c387
2016-09-30 09:52:03 -05:00
"timeago": {
"version": "1.5.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/timeago-1.5.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/timeago-1.5.3.tgz",
"dev": true
leaflet: bundle timeago JS module And start using it in DocumentRepair. Change-Id: I8d2b8af4d2e0dcc7cf8082c9d7adbc633df1c387
2016-09-30 09:52:03 -05:00
},
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"uglify-js": {
"version": "2.4.24",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/uglify-js-2.4.24.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/uglify-js-2.4.24.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"async": {
"version": "0.2.10",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/async-0.2.10.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/async-0.2.10.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"source-map": {
"version": "0.1.34",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/source-map-0.1.34.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/source-map-0.1.34.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"amdefine": {
"version": "1.0.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/amdefine-1.0.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/amdefine-1.0.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
},
"uglify-to-browserify": {
"version": "1.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/uglify-to-browserify-1.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/uglify-to-browserify-1.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"yargs": {
"version": "3.5.4",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/yargs-3.5.4.tgz",
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"resolved": "./node_shrinkwrap/yargs-3.5.4.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"dependencies": {
"camelcase": {
"version": "1.2.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/camelcase-1.2.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/camelcase-1.2.1.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"decamelize": {
"version": "1.2.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/decamelize-1.2.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/decamelize-1.2.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"window-size": {
"version": "0.1.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/window-size-0.1.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/window-size-0.1.0.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"wordwrap": {
"version": "0.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/wordwrap-0.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/wordwrap-0.0.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
}
},
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
"uglifyify": {
"version": "3.0.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/uglifyify-3.0.2.tgz",
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
"resolved": "./node_shrinkwrap/uglifyify-3.0.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
"dependencies": {
"convert-source-map": {
"version": "1.1.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/convert-source-map-1.1.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/convert-source-map-1.1.3.tgz",
"dev": true
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
},
"extend": {
"version": "1.3.0",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/extend-1.3.0.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/extend-1.3.0.tgz",
"dev": true
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
},
"minimatch": {
"version": "2.0.10",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/minimatch-2.0.10.tgz",
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
"resolved": "./node_shrinkwrap/minimatch-2.0.10.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
"dependencies": {
"brace-expansion": {
"version": "1.1.6",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
"resolved": "./node_shrinkwrap/brace-expansion-1.1.6.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"dev": true,
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
"dependencies": {
"balanced-match": {
"version": "0.4.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/balanced-match-0.4.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/balanced-match-0.4.2.tgz",
"dev": true
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
},
"concat-map": {
"version": "0.0.1",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/concat-map-0.0.1.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/concat-map-0.0.1.tgz",
"dev": true
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
}
}
}
}
},
"through": {
"version": "2.3.8",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/through-2.3.8.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/through-2.3.8.tgz",
"dev": true
loleaflet: Add uglifyify for minifying js code
2016-08-11 05:25:06 -05:00
}
}
},
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
"vex-js": {
"version": "2.3.2",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/vex-js-2.3.2.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/vex-js-2.3.2.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
},
"w2ui": {
"version": "1.4.3",
Remove devtools-detect as one of the dependencies Usage of this module was removed in 2bbab9bf943723c77498229676b93e9aba0185c7 Change-Id: I7fdde32cdf52fa0d33859fc4cda58d4daed40254
2016-12-15 02:42:45 -06:00
"from": "node_shrinkwrap/w2ui-1.4.3.tgz",
loleaflet: new dependency - autolinker - link what can be linked ... in annotations. Emails, phone numbers, email address and what not. We are not sending the generated markup, eg: the html <a> tags back to LO core, only the representation in the UI is linkified. Autolinker license: MIT https://www.npmjs.com/package/autolinker Change-Id: I8df3676a9eb6122884defb6bc3da87d30f993b04
2017-04-24 09:29:16 -05:00
"resolved": "./node_shrinkwrap/w2ui-1.4.3.tgz",
"dev": true
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
2016-08-03 02:47:12 -05:00
}
}
}
Reference in a new issue Copy permalink