-
Notifications
You must be signed in to change notification settings - Fork 122
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
Possible cyclic (circular) dependencies causing issues with Webpack #1092
Comments
Somehow |
Yes, I tried to use the single file bundle, but for some reason or other, it's very slow for webpack to process. I might try forking the project and making a webpack build to see if I can recreate the problem, at least to test new builds. Other than that small thing, everything works perfectly. |
Ok, it's slow, because it really needs to analyse the whole library, and can not drop things on the fly. |
Maybe it is an option for you to load Edit: this is what we do in Texture, too |
That's probably a good idea too. I wasn't really keen on splitting any libraries from the bundle, but the editor is a good exception because of the size. |
I've been using webpack to bundle substance. It worked with beta 6 until I tried beta 7.
I managed to get it to work again by changing the following:
I changed import { Component } form '../ui' to skip the re-export.
I've tried checking for cyclic dependencies with madge, but I think it crashes each time it hits one.
The text was updated successfully, but these errors were encountered: