-
Notifications
You must be signed in to change notification settings - Fork 113
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
Baklava identifies itself as Unknown in React #397
Comments
Hi @Enes5519, Thank you for the report. For confirmation: You use the same version on both CDN and NPM, right? |
@muratcorlu With the release of lazily loading baklava components (#320), we were expecting baklava not to work in React 16 and some versions of 17 since they handle React Lazy differently. We don't have any issues with the 18 though. |
I'm trying to debug this. I created a demo with React 16 and TS and apparently managed to run Baklava (beta75) in it without any issues. @Enes5519 can you check this: https://codesandbox.io/s/baklava-in-react-16-ts-ninfd0?file=/src/index.tsx I feel there is a problem about either TS version or tsconfig. |
Can you check if #449 fixes the issue here? |
🎉 This issue has been resolved in version 2.0.0-beta.77 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Describe the bug
Baklava not work in React 16. It identifies itself as "Unknown" component.
Possible: React Lazy Exports
To Reproduce
Screenshots
![Screen Shot 2023-02-02 at 11 01 12](https://user-images.githubusercontent.com/10272532/216265786-c91111d4-2736-46ed-9081-eab1c1a8255c.png)
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: