css-in-js
Cycle.js
css-in-js | Cycle.js | |
---|---|---|
3 | 11 | |
5,532 | 10,235 | |
- | -0.0% | |
0.0 | 4.1 | |
about 3 years ago | 5 months ago | |
JavaScript | TypeScript | |
MIT License | 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.
css-in-js
-
Front-end Guide
As you might have realized by now, the front end ecosystem is saturated with tools, and unsurprisingly, tools have been invented to partially solve some of the problems with writing CSS at scale. "At scale" means that many developers are working on the same large project and touching the same stylesheets. There is no community-agreed approach on writing CSS in JS at the moment, and we are hoping that one day a winner would emerge, just like Redux did, among all the Flux implementations. For now, we are banking on CSS Modules. CSS modules is an improvement over existing CSS that aims to fix the problem of global namespace in CSS; it enables you to write styles that are local by default and encapsulated to your component. This feature is achieved via tooling. With CSS modules, large teams can write modular and reusable CSS without fear of conflict or overriding other parts of the app. However, at the end of the day, CSS modules are still being compiled into normal globally-namespaced CSS that browsers recognize, and it is still important to learn and understand how raw CSS works.
-
Why are "CSS classes generally better for performance than inline styles." ~ from react docs
There are a myriad of CSS-in-JS tools, many of which are zero-runtime giving you all the benefits of authoring in a single file without the drawbacks of inline styles. That's how I prefer to do my CSS with React anyway... Vanilla Extract and/or Linaria are my current favorites.
-
Why was CSS-In-JS ever a thing?
One thing I think you're really missing is what the output is of CSS-in-JS. There are tens of CSS-in-JS frameworks that can output anything from: CSS Module like classes (Linaria, Vanilla Extract), Atomic Classes (StyleX, PreStyle), to the more traditional (Styled Components, Emotion) many with zero runtime cost (ie no JS bloat). That's why I say CSS-in-JS is primarily about developer experience... the output can often be whatever you want it to be.
Cycle.js
- Could angular possibly compile rxjs Ahead Of Time?
-
Can be the future of JSX be Functional first?
Seems like you might be interested in this
-
Front-end Guide
Cycle
-
[AskJS] Opinions In Favor of Coding Document Fragments in JS?
This is the standard way of going about things in Mithril and Cycle. Elm as well doesn't use an XML knockoff for view code- and as a fun fact, the original version of React didn't either.
- What is a really cool thing you would want to write in Rust but don't have enough time, energy or bravery for?
- Solid.js feels like what I always wanted React to be
-
callbag-rs: An implementation of the callbag spec
For example, an FRP framework (created by the same author who later wrote the callbag spec): https://cycle.js.org/
-
Does it make sense to use Scala.js/Laminar in the context of a startup?
TypeScript is relatively mainstream at this point, and I think that's good news. If you want to crank the type-safety and pure FP dials on it to 11, you certainly can do that. I have a project that I've based largely on this post, including the "hardcore" section. However, instead of Redux and otherwise plain React, I've chosen to use Cycle.js and the lessons from this post to use React in a very purely Functional Reactive Programming Way.
-
Flame: A PureScript front-end framework inspired by the Elm architecture
This post links to a PureScript project that is probably the easiest PS framework around.
ReScript + rescript-react is a good alternative. Less safe, waaaay more verbose; but backed by Facebook.
This is quite cute (in TypeScript though): https://github.com/cyclejs/cyclejs
And Yew is super cool, it goes the WASM route (in Rust): https://github.com/yewstack/yew
-
My Open Source Journey
From now on I was on what I would call a typical open source trajectory. I used the Cycle.js framework to rewrite my frontend and in that process I hit some walls. I eventually figured that the error was on my side and that I was just missing some information to avoid the error. To spare others the hours of debugging I started to contribute small patches to the documentation. At the same time I also found some missing features that I voiced in GitHub issues.
What are some alternatives?
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
RxJS - A reactive programming library for JavaScript
crisp-react - React boilerplate written in TypeScript with a variety of Jamstack and full stack deployments. Comes with SSR and without need to learn a framework. Helps to split a monolithic React app into multiple SPAs and avoid vendor lock-in.
MobX - Simple, scalable state management.
linaria - Zero-runtime CSS in JS library
Bacon - Functional reactive programming library for TypeScript and JavaScript
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
Most.js - Ultra-high performance reactive programming
ESLint - Find and fix problems in your JavaScript code.
Cycle.js (react-native) - Cycle.js driver that uses React Native to render
Rollup - Next-generation ES module bundler
Elm - Compiler for Elm, a functional language for reliable webapps.