@artsy/fresnel
css-modules
Our great sponsors
@artsy/fresnel | css-modules | |
---|---|---|
8 | 84 | |
1,201 | 17,327 | |
1.7% | 1.4% | |
7.2 | 5.5 | |
2 days ago | 6 days ago | |
TypeScript | ||
GNU General Public License v3.0 or later | - |
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.
@artsy/fresnel
-
Responsive Rendering With SSR
This! If you want to limit double rendering afterwards you could look into something like fresnel to automatically unmount unused breakpoints’ components after hydration.
-
How to combine React Native Web + responsivity + NextJS SSR, to get SEO
This article is extracted from this github discussion, which goes into greater detail on how to achieve this with the libraries Dripsy (a component design system) and Fresnel (SSR w/ media queries).
-
SSR for multiple breakpoints using React
Also, take a look at a library @artsy/fresnel, which uses a similar approach to solve CLS issues in server-side rendered applications.
-
Magnus UI vs. Dripsy - Chakra UI alternatives for React Native (+Web)
If you want both SSR and RNW, then you are not so lucky. But you can read my research of the options you have, in this discussion: How to combine React Native Web (RNW) + Responsive styles (media queries) + NextJS Server-Side Rendering (SSR), to get SEO on the web. If you don't want to make a compromise like the current options, there is a library called Fresnel, which has some promise to afford this combination. But it is not quite there yet. So please consider contributing to Fresnel in the RNW+NextJS compatibility issue or the useMedia() hook issue, so that Dripsy could be upgraded to use Fresnel again to support SSR.
-
How to use ChakraUI on native mobile?
Uses actual CSS breakpoints on web, to become responsive, even when using SSR. Uses Fresnel to achieve this. CSS breakpoints on web will rely on the mobile device's user agent for most cases. But since this can be inaccurate, it also uses pre-emptive server-side breakpoint generation. Basically, if the mobile user-agent cannot be accurately detected, Fresnel renders all media query breakpoints on the server (a bit of extra work for the server, since it might lead to rendering more components). So the client's browser will receive all breakpoints on first render and can immediately start rendering according to the correct ones. Instead of waiting for React to rehydrate before only then running the media queries with CSS-in-JS, which would have given latency and potentially unwanted visual side-effects. This becomes most acute when you are using SSR, and thus don't want to wait for rehydration on the client to start showing the responsively laid out content.
-
Full Stack Quiz Game with NextJS - My Journey
@artsy/fresnel - Lib to create media queries components in JSX.
css-modules
-
Use TailwindCSS prefixes for shared design system components
For many years, Culture Amp took the second option, and distributed shared components without compiled CSS. This meant that every app that consumed shared components needed to include the necessary CSS build tooling – at that time CSS Modules and node-sass – with a compatible version and configuration. This was relatively easy to set up, but over time proved difficult to maintain. When node-sass was deprecated in favour of (the much faster but slightly incompatible) Dart Sass, this demanded a difficult lock-step migration across all those codebases, which we have yet to achieve. And as new applications have switched to Tailwind for their own styles, they've had to continue to maintain those old build tools in parallel for the shared components' styles.
-
CSS Modules Still a Thing?
So CSS modules are a form of 3rd-party CSS-in-JS, where what you import are the class names, which are then usually obfuscated etc at compile time, and all the actual style declarations are (usually) compiled into a single css file or tag as part of the bundling process. You can read the og docs on'em here, and you've probably seen'em used in React like:
import styles from "./styles.css"; function Example(){ return (
Hello
); }They predate the ability to import non-js files in vanilla by a good while, and rely on the compile process to translate your
.css
files into.js
files that can be imported using whichever loader you use in your bundler.Import assertions are a vanilla way to import non-js files by telling the browser how to import them;
assert { type: "css" }
says to treat the file as CSS and create aCSSStyleSheet
,assert { type: "json" }
says to treat the file as JSON and create a JSON object - and hopefullyassert { type: "html" }
will hopefully arrive soon and create a#document-fragment
or something similar.Hope that clears it up!
-
An Overview of 25+ UI Component Libraries in 2023
Extensions of CSS: for example, Sass, Less, Tailwind, CSS Modules, to make stuff look a certain way on your own.
-
Creating a Component Library Fast🚀(using Vite's library mode)
The components are styled with CSS modules. When building the library, these styles will get transformed to normal CSS style sheets. This means that the consuming application will not even be required to support CSS modules. (In the future I want to extend this tutorial to use vanilla-extract instead.)
-
All 7 ways to deal with CSS most never tried
NextJS comes with built-in support for CSS Modules which allows you to scope your styles locally in individual components without worrying about name collisions or messing up other parts of the codebase.
-
Vanilla+PostCSS as an Alternative to SCSS
CSS modules are not to be confused with mixins, as they serve the opposite purpose. While mixins are components or functions to be reused globally, modules are style sheets with a local scope used in a similar way as styled components in React.
-
The Future of CSS
CSS Modules CSS Modules is a pre-processing step: by default, styles are scoped locally to the current component, and the transpiler ensures no conflicts.
-
CSS Style Guide for Web Dev?
But if you don’t want to use any of those yet, I would suggest at least using CSS modules to scope styling to components.
-
Why is tailwind so hyped?
Have you seen/tried CSS Modules? It's built into CRA and Vite, and it lets you write styles that are scoped to the component. I've heard people talk about using them alongside Tailwind, so I don't think it's necessarily an either/or situation, but to me it feels a lot more natural.
-
CSS: From Chaos to Order
You probably know what css-loader is and how it allows you to work with CSS modules. If this is not the case, then let me remind you what it is using the example of a React component:
What are some alternatives?
emotion - 👩🎤 CSS-in-JS library designed for high performance style composition
esbuild-plugin-solid
stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
postcss-nested - PostCSS plugin to unwrap nested rules like how Sass does it.
react-toastify - React notification made easy 🚀 !
styled-jsx - Full CSS support for JSX without compromises
react-native-media-query - Media queries for react-native and react-native-web
esbuild-solid - Example repo for building solid with esbuild
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
chakra-ui - ⚡️ Simple, Modular & Accessible UI Components for your React Applications
ChatUI - The UI design language and React library for Conversational UI