-
Notifications
You must be signed in to change notification settings - Fork 55
Fresh install - Cannot read property 'ref' of undefined #1065
Comments
Looks like issue with circular imports:
See any build, under Proposed solution: get rid of circular imports at all, however it will be not easy for |
@thinq4yourself, thanks a lot for reporting the issue! Could you, please, try the following version of Stardust and check if it solves your problem: 0.25.1-alpha. There we have prototyped a fix strategy, and would like at first to verify if it would work for your case. Also, could you, please, suggest which module resolution/loading algorithm is used for your project - is it ES or CommonJS? Thank you! |
HI there, @kuzhelov and thank you for the response! I will have some time in the next week or so to test again, since we are doing a release this week and fairly busy. We use ES6 and react-scripts |
@thinq4yourself, please, consider to check the following released stardust version where we have introduced the necessary fixes: v0.26. Also, we have added CI gate checks to prevent this problem from happening in future. Looking forward to hear results from you, to ensure that issue is resolved on your side as well. Thank you! |
Bug Report
Steps
A clear and concise description of steps to reproduce the problem.
1. Follow quick start
yarn add @stardust-ui/react
<Provider ... />
to root of the app2. Remove
<Provider ... />
and add components3. Remove this new potential UI from node_modules and package & reinstall
Expected Result
The result that you expected.
Actual Result
The actual result that happened 💣
The entire app crashes. This is a larger, existing app with fair+ sophistication at every level including debugging & error handling, and this is the first library that completely crashes the entire global app at bootstrap with very little to no information as to why, except perhaps in dependency conflicts or perhaps webpack issue. :( 💩
Browser output
Version
0.23.1
Testcase
Our react-scripts build/webpack config only slightly deviates from the core create-react-app's react scripts config.
Our app is not vanilla, but this low level error directly from your libraries bootstrap()... methods that break everything downstream in the build, is perplexing me.
Any expertise or direction in where to look most welcome, as we hope to adopt this in our core platform.
🙏
The text was updated successfully, but these errors were encountered: