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
[7.0] Default babel-register cache location to node_modules #5198
Comments
I'll take this one! |
What about the |
Also, I guess I'll have to write a couple of tests for this package? I couldn't find any in it's folder. I'd appreciate any guidelines to get started. |
I think the cache location should still be overridable ( I tried to add some tests (there). |
Yeah 👍 (dono if we really want to support |
@shubheksha The PR has been merged. Don't hesitate to tell me if anything is wrong with the tests. |
What is the current status of this issue? |
@shubheksha don't mean to step on your toes if you're still working on this. feel free to just close this pr, but its been a while and seemed simple enough that I thought I'd just make the PR. Not sure how this fits in with the long term cache plans, but would be a nice intermediate change. |
The config caching has a bit changed. @loganfsmyth worked on it. See #5608 for ex. |
why: easier to find since it's in node_modules, easy to clear all cache for all the tools that use it.
Move register cache file location to
./node_modules/.cache/babel-register
viahttps://github.com/avajs/find-cache-dir
Ref previous babel-loader PR: https://github.com/babel/babel-loader/pull/301/files as well as the current file (https://github.com/babel/babel-loader/blob/e9e37029e0c5905d8846f69d9a0c348f3d49fe50/src/fs-cache.js#L170), https://github.com/babel/babel-loader/pull/318/files
git checkout 7.0
and then make a branch off of that to PRmake build
after a source code change or better just runmake watch
in another terminal window to auto run babel while you are developingfindCacheDir({ name: "babel-register" })
and fallback to os/home/tmp dir.The text was updated successfully, but these errors were encountered: