-
Notifications
You must be signed in to change notification settings - Fork 16
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
Can't compile a local working bundle #14
Comments
Not sure what "linked to cosmos" means. This repo just bundles a React component, Cosmos is the built-in solution. The only case when you want to use this repo is if you don't want to use Cosmos and you want to integrate ComponentPlayground differently.
I can tell you from experience this probably means you bundled React more than once in your build (check out the bundle file to see for yourself). You can search the internet to see that React doesn't work with another React instance alongside. |
By linked to Cosmos I mean |
I can only assume you were trying to test some changes to ComponentPlayground inside Cosmos. I had the same problem since this is how I test ComponentPlayground changes: by linking the If this is what you're interested in, here is my flow: I tried linking My current workaround is to temporarily edit This way I can keep two terminals with both |
Thanks for clarification. The problem is most probably related to this issue: webpack/webpack#554 But it seems that it should already be resolved in the version of Webpack used here... I'll look into this in more detail. |
I cloned the repo and I tried to
npm run build
but the bundle produced doesn't seem to work when linked to cosmos. I locked the versions of all packages inpackage.json
to ensure I use the same vendor code, but it still throwswhen I run cosmos in browser. When used with the bundle from npm everything works fine. Any ideas?
The text was updated successfully, but these errors were encountered: