-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Lazy caching incompatible with webpack? #3
Comments
Should be fixed now. For future reference though, webpack itself isn't broadly adopted standard that qualifies as a factor in the versioning of a node module. After 3 million downloads of lazy-cache, I've had two issues about it, and both are from webpack users. It's worth considering that lazy-caching is just like any other language pattern and should be recognized by webpack. Until such time, I'd consider it a bug of webpack's and or browserify's. |
Thx! |
no problem, thanks for reporting! |
@kintel you can use unlazy loader in your webpack build if you're using libraries that use |
It looks like the lazy caching introduced in 0.2.2 is incompatible with webpack's static inclusion of dependencies, and should thus be bumped to a different version to avoid accidentally including it under the ^0.2.0 semver.
The text was updated successfully, but these errors were encountered: