-
Notifications
You must be signed in to change notification settings - Fork 211
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
Is anyone working on fixing these issues? #50
Comments
I'm pretty sure that's the case as the underlying source doesn't seem to be maintained. Just spent a few days integrating with a next.js project and there are a few major issues trying to deploy into production. |
what issues did you hit @chrisemoulton ? we try to keep on top of major issues that are reported |
hey @steve8708. Thanks for the quick response. I have two that keep persisting! Dev environment runs fine but I am looking to deploy into production asap. The first is an unescaped / traced back to the initial repo/css minification during build? The second is a type error in ./components/modals/index.tsx:21:14 I attached a list of the outdated sub dependancies in 2 as there are some potential compatibility issues at play? Chris |
@chrisemoulton would you mind elaborating more on the production deployment issues you see, I just tested full flow forking from |
Is this repo abandonned?
The text was updated successfully, but these errors were encountered: