gluecodes-framework
DISCONTINUED
css-modules
Our great sponsors
gluecodes-framework | css-modules | |
---|---|---|
17 | 84 | |
75 | 17,327 | |
- | 1.4% | |
0.6 | 5.5 | |
about 2 years ago | 6 days ago | |
JavaScript | ||
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.
gluecodes-framework
-
Deciding Between Solid and React for Production App
Thanks. Well, it is interesting from technical point of view not so much as a SAAS product to be totally honest. We tried to tackle too many aspects of frontend dev and made a product which is terribly hard to sell haha. Don't get me wrong, it's based on many cool concepts I still use on my current projects but it's over-featured. I guess, I went through a typical anti-lean startup journey (lessons taken). Anyway, it's still online: https://www.glue.codes and it's freemium. The only reason it's not open source is that I can't find the time to document it, but I guess I could just open the repo to public... Who knows, maybe someone finds it useful.
-
SolidJS Official Release: The long road to 1.0
I'm actually working on a rather large Solid project right now and will post it in our community when it's live. There are a lot of really neat things built on Solid, checkout Lume (https://github.com/lume/lume) which uses Solid for it's elements and even an IDE https://www.glue.codes/.
- FREE IDE dedicated to creating Bootstrap templates
-
How to build a food advisor UI for Strapi using GC & GraphQL
Static HTML has no built-in way to make it reactive. Hence GlueCodes Studio has a concept called extended tags which is named like: tagName + '-x' and has an embedded gc-as="listFieldPresenter" gc-provider="getCategories" gc-field="name" class="label">category name class="heading">Neighborhood class="filterSet"> gc-as="listItemPresenter" gc-provider="getNeighborhoods" class="filterItem"> type="radio"> gc-as="listFieldPresenter" gc-provider="getNeighborhoods" gc-field="name" class="label">neighborhood name class="heading">Language class="filterSet"> gc-as="listItemPresenter" gc-provider="getLanguages" class="filterItem"> type="radio"> gc-as="listFieldPresenter" gc-provider="getLanguages" gc-field="name" class="label">language name
- Looking for CSS wizards to contribute
-
5 Reasons why we chose to transpile to SolidJS instead of React
Choosing a relatively young framework with a limited support over Facebook's giant may seem like craziness. As a core developer at GlueCodes Studio, I was the one pushing towards taking the risk. The decision has been mainly driven by Solid's build-time DOM diffing flavoured with a very simple API. I really believe it's a natural replacement of Virtual DOM. I always believed that taking the compromise of re-rendering the whole tree when the app state changes just for a "developer's convenience" is a matter of time. There was Svelte on radar, but I'm rather in favour of JSX, especially because we already provide an abstraction layer for templating using HTML with our meta-framework specific directives. So, I thought it would be awesome to write UIs with this higher level of abstraction and export to more flexible JSX and if you wish, continue development out of our tool. Check out the docs for more info.
-
Front-end Studio powered by SolidJS
www.glue.codes
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.
@artsy/fresnel - An SSR compatible approach to CSS media query based responsive layouts for React.
styled-jsx - Full CSS support for JSX without compromises
esbuild-solid - Example repo for building solid with esbuild
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
caniuse - Raw browser/feature support data from caniuse.com
Cucumber.js - Cucumber for JavaScript
babel-plugin-tailwind-components - Use Tailwind with any CSS-in-JS library