-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
.babelrc changes do not bust cache #153
Comments
Don’t we disable using babelrc files? That is certainly our intent (and definitely worked at one point). |
It worked in V6 of this plugin.
Why do we want to disable them? They’re pretty common in the js community.
… On 5 Oct 2018, at 09:26, Robert Jackson ***@***.***> wrote:
Don’t we disable using babelrc files? That is certainly our intent (and definitely worked at one point).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Ahh, ember-cli-babel disabled, not broccoli-babel-transpiler. |
Should look into how https://babeljs.io/docs/en/config-files#apicache works internally in babel, see if we can leverage the same cache key that they use. |
to answer your question, ember-cli wants more control over the Babel plugins that get used by default, and using the babelrc file makes that more difficult which is why we disabled it there |
When using a
.babelrc
(or similar) config file for babel, changes to this file to not bust the persistent cache, causing compiled outputs to not change.Not sure the best way to handle this as https://babeljs.io/docs/en/config-files lists various techniques babel goes through to find config file, but it could be as simple as including their hash in the cache key.
The text was updated successfully, but these errors were encountered: