Changes to the `.babelrc` file do not invalidate the cache
See original GitHub issueI’m submitting a bug report.
Current Behavior
When using cacheDirectory: true
the cache does not get invalidated between changes to .babelrc
contents. Disabling the cache works as expected and changes to .babelrc
are reflected in the generated bundle.
Expected Behavior
When using cacheDirectory: true
the cache should be invalidated between changes to the .babelrc
file as mentioned in the docs.
Versions
- node: 9.5.0
- npm: 5.6.0
- webpack: 3.11.0
- babel-loader: 8.0.0-beta.1
- @babel/core": “^7.0.0-beta.40”,
- OS: Windows 10 Pro 64-bit
Configuration
{
loader: 'babel-loader',
options: {
cacheDirectory: true,
},
}
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Config Files - Babel.js
Babel has two parallel config file formats, which can be used together, ... .mjs . .babelrc file, with no extension. package.json files, with...
Read more >how to clear babel cache? - Stack Overflow
If you are using a babel.config.js file which looks like below. You can turn off the cache by passing false to api.cache(false)
Read more >babel cache folder - The Case Cam
Currently Babel will invalidate the cache when you change your config or the file content, but otherwise deleting the cache folder is the...
Read more >Parcel 2 beta 3
On the ESBuild benchmark, Parcel is now ~10x faster without Terser, ... When any of these change, Parcel needs to invalidate the cache...
Read more >Changelog | Meteor API Docs
Don't apply babel async-await plugin when not running on Fibers PR. by ... it no longer relies on file watchers to detect the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This seems to work now, using
beta.2
. 👍I released beta.2 which should fix the problem that was introduced in beta.1 If it still does not work, we need to investigate more.