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

Support for "exposeAll" option #10

Open
VanCoding opened this issue Oct 10, 2016 · 1 comment
Open

Support for "exposeAll" option #10

VanCoding opened this issue Oct 10, 2016 · 1 comment

Comments

@VanCoding
Copy link

When I try to use browserify-cache-api on a bundle that has "exposeAll" set to true, it gives me an "ENOENT : no such file or directory" error that I don't get when I either set exposeAll to falso, or do not use cache-api. So I think cache-api does not support bundles with that option set to true right now.

Would that be easy to support? I'd do it myself if you gave me some hints what'd need to be changed.

@Macil
Copy link
Collaborator

Macil commented May 28, 2022

What exactly is the behavior of the exposeAll option? It looks like it's intentionally undocumented in Browserify (browserify/browserify#1296, browserify/browserify#1480). Does the PR #11 solve jsdf/browserify-incremental#22, and make caching work correctly in that case? (Could a test be made?)

If this is still an issue for someone and they can address the above then I'll merge a PR, and maybe we can see about adding a maintainer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants