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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃摙 Status of Linaria and road to 2.0 #582
Comments
2.0
馃摙2.0
2.0
Is the new evaluation strategy already used in the 2.0 alpha? Or is it necessary to opt-in to it? |
@Jayphen not yet, you can configure it as it is said #447 (comment) |
@jayu I've just tried that with the alpha and it did not break anything. I am not sure how to even know if it is using the new strategy or not. Edit: just tried it on a different app that I migrated from Emotion. With the old strategy it was giving some strange errors during the build that I couldn't pin down. With the new strategy those errors go away. |
What about a build time penalty? Linaria 1.3.x adds 7-8 minutes to a build process and 30-40 seconds to a rebuild on a middle size project, it's why we moved to Emotion. |
There is chance to list work that need to be completed for v2 ? Community could help to implement some changes if these are well-defined. Maybe you consider adding Github Funding for a project ? |
@blasterpistol we added a couple of optimizations so it should be faster now. You have to check it on your project :D @chyzwar Here is a milestone that contains issues that should be resolved https://github.com/callstack/linaria/milestone/7 before the stable release. |
The migration guide 404s. |
I just filed #681, which I think might be relevant to include in your 2.0 roadmap. Given the nature of |
|
Status Note
Recently @Anber was working on a new evaluation strategy called shaker. The goal was to make Linaria more flexible and reliable.
All work regarding shaker had been releasing with
1.4.0
tag, currently inbeta
stage.Meanwhile, we wanted to introduce some breaking changes, so we decided to release
2.0.0
inalpha
stage.All
1.4.x
work can be found on1.4.x
branchCurrent
master
branch contains work that is planned to be released as2.0.0
. It is a continuation of1.4.x
but with some breaking changes. You can track progress on new major version in2.0.0
milestone.We will release stable
1.4.0
once we finnish shaker effort. Documentation for1.4.x
can be found on1.4.x
branchWe will release stable
2.0.0
just after stable1.4.0
but with breaking changes documented in2.0.0
migration guideThe text was updated successfully, but these errors were encountered: