-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
Errors after dependency upgrades #26
Comments
Ouch! Sorry for this. I'll investigate ASAP 🏃 |
I've published 1.8.3 that should fix your issue. Could you try it and let me know please? 🙂 |
BTW I'm not sure why it was not working in your app because |
Yeah, I'm a little confused as to why it wasn't working properly in the app since it is a dependency. It worked for client-side navigation but not serverside renders. I figured it was a wider issue as it wasn't working properly in runkit either. When I was looking at the layout of my project's The good news is that 1.8.3 fixes the problem! Thanks for the speedy fix, I really appreciate it! |
Are you using When installing, the package with yarn, I get |
Ah, we do use I'll mark this as closed since the issue seems to be resolved. |
Which version are you using? |
We're using npm |
After #25 was merged I've noticed issues with serverside renders on my application - mainly they do not work correctly when I use
react-easy-crop
due to arequire
statement seeking a dependency that is not immediately available.This is the stacktrace for my error:
This is caused by the fully compiled
styles.js
including the@emotion/styled-base
dependency like this:This error can also be seen when trying to run the package in runkit: https://npm.runkit.com/react-easy-crop
The text was updated successfully, but these errors were encountered: