summaryrefslogtreecommitdiff
path: root/loleaflet/package.json
diff options
context:
space:
mode:
authorPranav Kant <pranavk@collabora.co.uk>2016-08-03 13:17:12 +0530
committerPranav Kant <pranavk@collabora.co.uk>2016-08-03 15:45:01 +0530
commit484c664445ab09a47704ccd84bbd0597b29b0c6d (patch)
tree2a06be1e4aece8ac4145805a7b86d3510df867b6 /loleaflet/package.json
parentebacc6624a778ac75feaae78da0c67b387a048ba (diff)
loleaflet: Shrinkwrap and shrinkpack; local dependencies tarballs
Using npm-shrinkwrap, we are locking in our dependency tree completely, leaving no scope of being affected by any regression in any of the dependencies. In other words, all of the dependency tree is dumped in npm-shrinkwrap.json file. Using shrinkpack, we are also committing these tarballs of dependencies in node_shrinkwrap/, so that, we are not depending on npm registry at all during our build process. Since these are just tarballs, its also better space-wise than committing node_modules/ per se. Developers when want to update any dependency should bump the version in package.json, and also commit the new copy of tarballs in node_shrinkwrap/. See: https://github.com/JamieMason/shrinkpack for more info.
Diffstat (limited to 'loleaflet/package.json')
-rw-r--r--loleaflet/package.json1
1 files changed, 1 insertions, 0 deletions
diff --git a/loleaflet/package.json b/loleaflet/package.json
index 7df90a18b..e45eb4ba7 100644
--- a/loleaflet/package.json
+++ b/loleaflet/package.json
@@ -27,6 +27,7 @@
"l10n-for-node": "0.0.1",
"malihu-custom-scrollbar-plugin": "3.1.3",
"select2": "4.0.1",
+ "shrinkpack": "^0.13.1",
"smartmenus": "1.0.0",
"uglify-js": "~2.4.16",
"vex-js": "2.3.2",