-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Element 2.0.0-alpha.1 released 🎉 #7305
Comments
thanks for the awesome work, please can you tell me how to migrate from version 1.4 to 2 |
@wvllvw Updated. |
@Leopoldthecoder thank you brother, You're doing a great job. |
@wvllvw Basically you don't need to change anything in webpack config. Just uninstall 1.4 and install 2.0.0-alpha.1 (remember the |
Nice work!!! |
validation related functionalities are still not good enough, |
I am experiencing what seems like styling issues when pulling in only Can anyone confirm datepicker is not working by itself with 2.0 alpha? Other than that, it's awesome!! |
2.0单独引用 input 会报下面的错 found in ---> |
|
@Chinese1904 We haven't updated the standalone packages. We'll do that when we come to the final release of 2.0.0. |
Also in cards |
@Leopoldthecoder quick question, it seems like standalone packages have not been updated yet. Any eta on those? Thanks so much! |
Changelog
https://github.com/ElemeFE/element/releases/tag/v2.0.0-alpha.1
Documentation
http://element.eleme.io/2.0/#/en-US/component/installation
Installation
Tips
theme-chalk
is included in2.0.0-alpha.1
, feel free to try it out. It is not recommended to use this version in production though, because it's still in alpha stage.Some components (e.g. Table) are still being upgraded, and we'll ship them in future releases. Thank you for your patience.
Migration
If you wish to migrate from 1.4 to 2.0.0-alpha.1, please refer to the 'Breaking changes' section in changelog. When the final 2.0.0 version is released, we hope to be able to provide a migration tool for your convenience (fingers crossed).
The text was updated successfully, but these errors were encountered: