postcss-font-family-system-ui
emotion
postcss-font-family-system-ui | emotion | |
---|---|---|
1 | 52 | |
94 | 17,186 | |
- | 0.3% | |
6.3 | 5.8 | |
2 days ago | 6 days ago | |
JavaScript | JavaScript | |
Creative Commons Zero v1.0 Universal | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
postcss-font-family-system-ui
-
Babel is used by millions, so why are we running out of money? · Babel
I am Jùnliàng, a Babel contributor since 2019. I would like to share my perspective here.
GH is a platform where people collaborate on developing softwares, so the contribution graph is engineering-biased. But operating an OSS, especially like Babel which is serving millions, is just like running a company. In a company we have different roles, none of roles is more important than the others. In Babel team, Henry spends most time on reaching out to contacts in companies, giving talks, syncing with different projects in the ecosystem, offering mentorship to junior contributors like me. None of these is visible on GH but they are vital to sustain the project, to attract both new company sponsors and contributors.
2020 is a hard time for any reasons. Before we talk about funding with team, Henry has already voluntarily pooled less money ($11k to $8k) and another long-time core contributor Brian (https://github.com/existentialism) stopped taking money. While this helped bumped up our balance, everyone taking less is a dangerous signal to an OSS: maintainers constantly fighting with financial insecurity may burn out or stop maintaining in order to recover from the mental pressure about "I am responsible for this".
I maintained small side projects like (https://github.com/JLHwung/postcss-font-family-system-ui), where the feature set is frozen and most maintenance works can be automated by bots. This is quite unlike Babel: The feature is open-ended because the language is evolving. Various edge cases should be take cared. Tradeoffs between spec compliance and output code size should be made. It is not a side project that I can dedicate part time efforts like 10hrs/week to work on.
Speaking for myself, I spend around 40hrs/week to meet my own productivity requirements. I don't think I deserve more than other paid team members because everyone has different time constraints and we don't track work time meticulously.
To avoid burn-out and not let Babel consume all my energy, I spare some time on encoding Chinese characters in Unicode, which, just like Babel, has profound impacts on ecosystem but long overlooked and underfunded. I helped submitted hundreds on characters in IRGN2487 (https://appsrv.cse.cuhk.edu.hk/~irg/irg/irg56/IRGN2487UKData...).
emotion
-
Creating Nx Workspace with Eslint, Prettier and Husky Configuration
emotion [ https://emotion.sh ]
- Why is does modern HTML/CSS seem so complex and convoluted? (details in comment)
-
How are folks feeling about the React team's push toward server components?
dang, I never thought about this implication, and I googled the emotionjs repo there's a currently-active open issue regarding this https://github.com/emotion-js/emotion/issues/2928
-
I created a Zero-Runtime CSS-in-JS Library Compatible with Next.js App Router and RSC
Over my years of working with React, I’ve loved using CSS-in-JS libraries like Emotion and Styled-components. However, their inherent performance overhead from injecting CSS at runtime and their incompatibility with the latest Next.js features such as App Router and React Server Components (RSC) have always been a nagging issue for me.
-
Next.js App Directory Architecture First Impressions
An early difficulty I encountered was using UI component libraries like Mantine and Material UI in the new architecture. After looking through some GitHub issues, the culprit is Emotion, a package many component libraries rely on that does not support server rendering.
- How are you styling in NextJS?
-
CSS Style Guide for Web Dev?
In general I recommend using styled-components or emotion. These directly attach CSS to your components in a scoped way so that your CSS files aren’t stepping on each other’s toes all the time and make sure styling is colocated with the component.
-
Server Components
I ran into this problem as well. The root cause as I understand it is emotion: https://github.com/emotion-js/emotion/issues/2928
-
CSS In JS - The what, why and How's
While integrating component libraries, they may not give you full control over the order in which styles are inserted. (Example issue).
-
Lets create something neat together!
Vanilla Extract (CSS Framework) (Alternative: Emotion)
What are some alternatives?
Tailwind CSS - A utility-first CSS framework for rapid UI development.
Babel (Formerly 6to5) - 🐠 Babel is a compiler for writing next generation JavaScript.
JSS - JSS is an authoring tool for CSS which uses JavaScript as a host language.
at-rule-packer - Merge media queries (@media), @supports, and other duplicate At-rules together under a single block.
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
Nextcloud - ☁️ Nextcloud server, a safe home for all your data
styled-jsx - Full CSS support for JSX without compromises
autoprefixer - Parse CSS and add vendor prefixes to rules by Can I Use
linaria - Zero-runtime CSS in JS library
Sass - Sass makes CSS fun!
PostCSS - Transforming styles with JS plugins