This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(serenity-bdd): changed the default location of the cache director…
…y so that npm doesn't prune it If your project uses `package-lock.json` and npm >= v5, running `npm install` removes any directories not listed in `package-lock.json`. Since this also includes the Serenity/JS cache directory (originally located at `node_modules/@serenity-js/cache`), it means that, if you were using that setup, you'd need to re-download the Serenity BDD reporter jar after every `npm install`. The default location of the cache directory has now been changed to `node_modules/@serenity-js/serenity-bdd/cache` to avoid this issue. See npm/npm#16853
- Loading branch information
Showing 1 changed file with 1 addition and 1 deletion.