-
Notifications
You must be signed in to change notification settings - Fork 0
Future npm package plans #7
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
Comments
@aldanor bump |
@levithomason Hi, I must have missed the notification. Yes, I think there's no problem in transferring the npm package over if you'll describe how to proceed with it, I'm not planning to continue working on this as of right now since I've got a boatload of other stuff to finish :/ Glad someone's doing the official integration (attempt number 5?), hope this one takes off! |
Awesome, thanks. If you want to add me as a package owner that should take care of it for now: npm owner add levithomason semantic-ui-react Once we're ready to publish, I can deprecate the current release and publish the new one. |
https://www.npmjs.com/package/semantic-ui-react @levithomason Done and done 🐼 |
Hope that solves it! |
😄 that was quick! |
Hey there, glad to find another SUI + React project out in the wild. I'm the author of Stardust, which is now the official SUI React integration. We've outlined our path to migrating to the official Semantic-Org on this issue. Part of this includes publishing a new NPM package which would ideally have the current name your package,
semantic-ui-react
. This would allow us to follow the current official package naming scheme:semantic-ui-css
semantic-ui-less
semantic-ui-sass
semantic-ui-ember
...etc
If there are no plans to continue work on
semantic-ui-react
, would you be willing to consider transferring the package for official use? The package name is not a deal breaker for us, but it would be a big help and super appreciated.No matter what you decide, I'd love to have your eyes and hands on official integration as well ;)
The text was updated successfully, but these errors were encountered: