Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default to package-lock.json and yarn.lock for environmentHash #209

Merged
merged 2 commits into from
Dec 11, 2017

Conversation

mzgoddard
Copy link
Owner

@mzgoddard mzgoddard commented Dec 11, 2017

Close #203

  • Remove deprecated environmentPaths option

If files and directories are not specified to the environment hash
feature, it will try hashing package-lock.json npm's lock file and
yarn.lock yarn's lock file. It will hash both, or just one if only
one exists. A project going from one to both, will create a new
environment hash.

If neither lock file is available it will fall back to the previous
defaults, hashing package.json and node_modules.

If files and directories are not specified to the environment hash
feature, it will try hashing `package-lock.json` npm's lock file and
`yarn.lock` yarn's lock file. It will hash both, or just one if only
one exists. A project going from one to both, will create a new
environment hash.

If neither lock file is available it will fall back to the previous
defaults, hashing `package.json` and `node_modules`.
@mzgoddard mzgoddard merged commit d3ffdc1 into master Dec 11, 2017
@mzgoddard mzgoddard deleted the environment-hash-lock-default branch December 11, 2017 03:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant