stencil
css-modules
Our great sponsors
stencil | css-modules | |
---|---|---|
55 | 86 | |
12,292 | 17,368 | |
0.8% | 0.5% | |
9.9 | 5.5 | |
4 days ago | 18 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.
stencil
- Ajout de l'auto-complétion sur les Web Components avec Stencil
-
Making Web Component properties behave closer to the platform
First a disclosure: I never actually used Stencil, only played with it a bit locally in a hello-world project while writing this post.
-
Plasmic.app – the visual builder for your tech stack
This is my main concern too.
I don't understand why tools like this "pick a winner" with a specific framework instead of rendering to Web Components with a framework wrapper, or using something like Stencil[1] that can render to any framework.
[1] https://stenciljs.com/
-
Design Systems with Web Components
I was recently able to sit down with some of the core members of Ionic, who also created Stencil a toolchain for building Design Systems and Progressive Web Apps. We talked at great length how typically companies are approaching Ionic from a Design Team and need help building components. As a developer I wanted to talk about the Web Components that are used within the Design System first. There was a decent amount of surprise, so I thought I would break down what a Design System is and why it doesn't matter which end you start with, as long as you have both your Design and Development teams working together to build your Design System.
- Nue: A React/Vue/Vite/Astro Alternative
-
If Web Components are so great, why am I not using them?
Examples like this bug me. The React example is using a high level abstraction, the web component is directly using the API. A more accurate example would show how those React calls eventually boil down to document.createElement()
I don’t think the Web Components API was meant to be used directly all the time. You can use a framework like StencilJS:
https://stenciljs.com/
- Use Stencil / the ionic framework with emberjs [video]
-
World Wide Web Wars
You might say that this is the same vicious cycle as JavaScript frameworks. That's wrong, because Web Components are interoperable by design. Choosing Stencil or Lit or any other library is a development convenience that has little to do with the interoperability of the resulting components.
-
React Component in vue/angular
Not sure about Vue but you can in Angular, though my experience with React components in Angular has not been pleasant. Libraries such as Stencil allow you to create native Web Componets from React components.
-
Is there a plugin that abstracts registering web components with React?
I guess my problem is more specific to my overall architecture. I have components that when are placed in the DOM, have props rendered on them by their parent elements. I'm using stencil to do this.
css-modules
-
Selectors for Humans, Hashes for Machines
One aspect of CSS modules that I truly appreciate is its ability to compress class names into very short hashes. This feature allows me to keep my CSS selectors as long and descriptive as needed, while still compressing them into concise three or four character hashes. It aligns with my rule for CSS: selectors should be written for human readability, but compressed for machine efficiency.
-
Architecture: Micro frontends
Use methodologies such as BEM, and technologies including CSS modules, CSS-in-JS, and Shadow DOM to isolate the styles of each micro-application and prevent conflicts, thus ensuring reliable encapsulation and modularity.
-
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.
- I'm Writing CSS in 2024
-
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.
What are some alternatives?
lit - Lit is a simple library for building fast, lightweight web components.
emotion - 👩🎤 CSS-in-JS library designed for high performance style composition
Svelte - Cybernetically enhanced web apps
esbuild-plugin-solid
vite-ssg - Static site generation for Vue 3 on Vite
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
catalyst - Catalyst is a set of patterns and techniques for developing components within a complex application.
postcss-nested - PostCSS plugin to unwrap nested rules like how Sass does it.
shoelace-css - A collection of professionally designed, every day UI components built on Web standards. SHOELACE IS BECOMING WEB AWESOME. WE ARE LIVE ON KICKSTARTER! 👇👇👇
@artsy/fresnel - An SSR compatible approach to CSS media query based responsive layouts for React.
webcomponents - Web Components specifications
styled-jsx - Full CSS support for JSX without compromises