-
Notifications
You must be signed in to change notification settings - Fork 261
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 it alive? #688
Comments
@rauchg, @nkzawa, @leo, @giuseppeg pay attention please |
@artalar sadly, this project is not adequately maintained to be relied upon anymore. I've put many hours into into high effort suggestions and PR's that fix critical bugs, only for them to languish for months without a merge or sometimes even review: These important suggestions haven't been actioned in a year:
I really gave |
I find out that I never liked Also to improve the project further, we could deprecate |
I hope we will see some movement in the near future, I don't want the death of styled-jsx, but the current silens of mainteners looks not good. P.S. @divlo currently u haven't the rights to accept PRs? |
Hi everyone! This package is still alive and we fix issues as they come up if they relate to Next.js. Please open any bugs you may be experiencing on the Next.js issue tracker specifically, which will give them more visibility. RFCs should also exist as a Next.js discussion as that'd draw the most attention to get the upvotes necessary to implement the feature. I'll close this issue, but please CC me on any issues that need attention! |
Hi there, styled-jsx is an interesting lib with good API, it recommended by official docs of next.js and already integrated with it (also hosted in the Vercel GH org).
But it looks a little neglected. I was created #650 and #651 a long time ago but still have no reactions. This repo has other issues without any reactions. Why it happened, is it a lack of maintainers?
The text was updated successfully, but these errors were encountered: