This is to accommodate FireFox. The build process and resulting minified files should be consistently similar across environments in order to meet FireFox's approval.
Going forward, any needed updates to these packages should be handled manually.
The initial solution was to simply remove the caret from our package.json but this resulted in incompatibilities, as we saw on CircleCI:
Rather than wading through what combination we needed, since the current versions that we have installed are working, it made the most sense to go with them and just tie them down via Shrinkwrap. Except that Shrinkwrap doesn't support a modern version of node:
A consistent shrinkwrap tool Note: npm >= 3 is currently not supported.
It's not fair to expect everyone to downgrade their local version of NPM just because it's not supported. My current version is 4.0.5.
The only real choice at this point was to move to Yarn. CircleCI, the tool we use for continuous development, has great support for Yarn, so this works out great.
This is to accommodate FireFox. The build process and resulting minified files should be consistently similar across environments in order to meet FireFox's approval.
Going forward, any needed updates to these packages should be handled manually.
The initial solution was to simply remove the caret from our package.json but this resulted in incompatibilities, as we saw on CircleCI:
Rather than wading through what combination we needed, since the current versions that we have installed are working, it made the most sense to go with them and just tie them down via Shrinkwrap. Except that Shrinkwrap doesn't support a modern version of node:
It's not fair to expect everyone to downgrade their local version of NPM just because it's not supported. My current version is 4.0.5.
The only real choice at this point was to move to Yarn. CircleCI, the tool we use for continuous development, has great support for Yarn, so this works out great.