-
Notifications
You must be signed in to change notification settings - Fork 13
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
Migration to Bulma v1.0 #295
Conversation
This looks very promising already 😊. |
Is there any plan to progress here? |
Yes! There are plans to officially migrate from Bulma v0.9.x to Bulma v1. For the moment @kikuomax and I are working on completing the TS migration which will be published in v0.2.0 buefy-next (See #151). There are also some bugs that will need fixing from versions 0.2.x to 0.3.x (Bulma v1 support) Thanks @gmercey for taking the migration on early! It looks very promising |
I just updated the PR to resolve conflicts. Overall everything looks good on my end, I have my work running on production for a little while now. |
Sweet! Have you run into any issues? |
@gmercey I will look into your PR after releasing v0.2.0 which will mostly consist of the TypeScript migration. |
There are a few button states (e.g: primary outlined loading) that need some teaks but overall the CSS works great. I also keep my branch in sync with the dev branch, and so far, I didn't encounter any issues. |
Rebasing notes: - Hoists `bulma` to the workspace root. - Adds `--load-path=../../node_modules` to the `sass` command in the `build:scss` command, because `bulma` is likely installed in the workspace root. - (docs) Removes `bulma-css-vars` from `docs`'s dependencies, because it requires Bulma v0.9. So the extension page of `bulma-css-vars` no longer works.
Migrating component and documentation to Bulma V1.0
https://bulma.io/documentation/start/migrating-to-v1/