-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Actual package name #324
Comments
They're all the same in terms of functionality and they'll all be maintained. In the future only one package will remain |
The versioning started from |
Thank you! |
The namespace for |
Why did you change the pkg name from |
Because in the future we will support different frameworks, |
I'm a little confused. I see three similar packages in npm:
Which of these packages should I use? What are the differences? Will the others be deprecated?
And why did the versioning start all over again?
Thank you for your hard work!
The text was updated successfully, but these errors were encountered: