Skip to content
Permalink
Browse files
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
jan-molak committed Jun 30, 2020
1 parent 0b1469d commit 54d6dd4eb9c380c8fa917ffc4f2f23f98c9afcba
Showing 1 changed file with 1 addition and 1 deletion.
@@ -17,7 +17,7 @@
export const defaults = {
artifact: 'net.serenity-bdd:serenity-cli:jar:all:2.1.10',
repository: 'https://jcenter.bintray.com/',
cacheDir: 'node_modules/@serenity-js/cache',
cacheDir: 'node_modules/@serenity-js/serenity-bdd/cache',
sourceDir: 'target/site/serenity',
reportDir: 'target/site/serenity',
featuresDir: 'features',

0 comments on commit 54d6dd4

Please sign in to comment.