Navigation Menu

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

fix: correctly calculate cacheIdentifier from lockfiles #5113

Merged
merged 3 commits into from Jan 30, 2020

Conversation

sodatea
Copy link
Member

@sodatea sodatea commented Jan 28, 2020

follow up of #3865
fixes #4438

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Docs
  • Underlying tools
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

Other information:

The previous implementation is based on the assumption that config files
have precendences, e.g. `.eslintrc.js` will take higher precendence
over `.eslintrc`, and only one will take effect.

This is not accurate however. For example, babel relies on both babel
config and browserslist config, so we need to deal with 2 config files.
@pksunkara pksunkara merged commit d11ecc2 into vuejs:dev Jan 30, 2020
mactanxin pushed a commit to mactanxin/vue-cli that referenced this pull request Feb 11, 2020
* fix: correctly calculate cacheIdentifier from lockfiles

follow up of vuejs#3865
fixes vuejs#4438

* Revert "fix: correctly calculate cacheIdentifier from lockfiles"

This reverts commit dbce88b.

* fix: should take all configFiles and lockfiles into account

The previous implementation is based on the assumption that config files
have precendences, e.g. `.eslintrc.js` will take higher precendence
over `.eslintrc`, and only one will take effect.

This is not accurate however. For example, babel relies on both babel
config and browserslist config, so we need to deal with 2 config files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

babel-loader cache won't be updated after updating transpileDep with npm
2 participants