We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm submitting a feature request
Is there any possibility to expose the cache implementation as a direct export? Or as a separate package?
A form of this is already done in https://github.com/viankakrisna/loader-fs-cache but already seems to be somewhat out of sync with this version. It's used in eslint-loader as their caching mechanism.
Pulling it directly from here seems like a cleaner solution and I imagine there are multiple other packages that would like to use it.
I realize that there's a possibility to import it like import cache from 'babel-loader/lib/cache' but that seems iffy and could break easily.
import cache from 'babel-loader/lib/cache'
If implementing it would most likely need to:
transform
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I'm submitting a feature request
Is there any possibility to expose the cache implementation as a direct export? Or as a separate package?
A form of this is already done in https://github.com/viankakrisna/loader-fs-cache but already seems to be somewhat out of sync with this version.
It's used in eslint-loader as their caching mechanism.
Pulling it directly from here seems like a cleaner solution and I imagine there are multiple other packages that would like to use it.
I realize that there's a possibility to import it like
import cache from 'babel-loader/lib/cache'
but that seems iffy and could break easily.If implementing it would most likely need to:
transform
option Custom transform option not supported #832.The text was updated successfully, but these errors were encountered: