Skip to content
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

Project Status #387

Open
lxsmnsyc opened this issue Dec 22, 2020 · 4 comments
Open

Project Status #387

lxsmnsyc opened this issue Dec 22, 2020 · 4 comments

Comments

@lxsmnsyc
Copy link

I would like to ask the current status of Styletron? There have been commits in this repository, but the last commits to one of the package was 8 months ago, and the last release was over a year now. There have been issues which needs to be addressed, and I am afraid that some projects may be affected by those issues. There are also frameworks (namely, Base) which relies on the Styletron libraries.

@tajo
Copy link
Member

tajo commented Dec 22, 2020

We still use Styletron in Base Web (and Uber) so always keeping track of issue. I have a plan to look into #383 next week.

There are not many updates because we are pretty happy with the current feature set (we made a lot of changes a year ago, including a major version).

Also, always happy to review PRs.

@lxsmnsyc
Copy link
Author

lxsmnsyc commented Dec 22, 2020

@tajo Thanks for the quick reply. Follow-up question: What are the plans for the monolithic package? Is it something that we will choose over atomic?

edit:
About the issue, we are using Base Web, combined with Next JS. Although we don't really have to deal with styletron directly, we are indirectly affected by the issue. It was personally disappointing that the issue has not received any reply for months and we had to deal with some work arounds for keyframes we created customly, the problem still persists on Base Web internally and therefore our site's UI remains broken for months in which we can't address them as devs. I hope this gets fixed.

@tajo
Copy link
Member

tajo commented Dec 22, 2020

@tajo Thanks for the quick reply. Follow-up question: What are the plans for the monolithic package? Is it something that we will choose over atomic?

Up to you. They have different trade-offs. Base will probably keep using the atomic engine internally since it's stricter so our components work in both worlds. It's possible that we deprecate atomic at some point but no timeline.

the issue has not received any reply for months...

It's been reported Nov 16th ~ 1 month ago?

We are currently (hopefully temporarily) 2 people team and have a lot of other projects to juggle. If bug is not impacting our internal apps or a majority of outside projects it has to wait. Both projects are OSS, having a PR, even if it's just a failing test, would greatly help.

@lxsmnsyc
Copy link
Author

lxsmnsyc commented Dec 22, 2020

Apologies for the exaggaration, debugging seems to affect my time perception 😅

We are currently (hopefully temporarily) 2 people team and have a lot of other projects to juggle.

I understand. Although, these could (possibly) negatively affect the userbase. With broken UI (although minor), we are now inclined to use other frameworks. Base Web is still great for producing design systems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants