I have been using http-mock with Ember CLI. Today I generated a new http-mock with
ember generate http-mock myobject
I found afterwards that my package.json file had been updated from express 4.12.4 to 4.13.0
- "express": "^4.12.4",
+ "express": "^4.13.0",
Our Ember CLI version has remained constant, it just so happens express released a new version (https://github.com/strongloop/express/releases/tag/4.13.0) between the first time we used http-mock and today.
We would rather manage dependency changes by themselves as and when we want to, but still be able to create new http-mock's when we want them. Can I run the command slightly differently to prevent express upgrading it's version?
This was identified as undesired behavior in Ember CLI 1.13.1 and has been fixed as an enhancement under this pull request https://github.com/ember-cli/ember-cli/pull/4452.
To stop http-mock from updating express etc the answer is to upgrade to the next version of Ember CLI after 1.13.1, when it is released.