nw.js
css-modules
nw.js | css-modules | |
---|---|---|
58 | 86 | |
40,129 | 17,392 | |
0.2% | 0.3% | |
9.1 | 5.2 | |
4 days ago | about 1 month 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.
nw.js
-
Linux 6.9 Set to Drop the Old NTFS File-System Driver
> FUSE drivers are slow, but "wildly slow" is an overstatement.
I can confirm this, I've played RPGMaker M{V,Z} games natively by swapping out the copy of NWJS¹ it shipped with and running it through a CIOPFS² mount.
1: https://nwjs.io/
2: https://www.brain-dump.org/projects/ciopfs/ / https://github.com/martanne/ciopfs
-
How to play this on a Chromebook through Linux Itch.io
Go to this page to download NW.js https://nwjs.io/.
-
Win 7 no longer supported?? Please no!
(Step 7 will not be necessary once https://github.com/nwjs/nw.js/issues/5769 is completed)
-
Linux nw.js version of my game very slow, anyone knows a solution to this?
The support for WebGL in NW.js on Linux has been broken since NW.js 0.72.0: https://github.com/nwjs/nw.js/issues/8043
-
What would be the current recommended way to publishing an html5 game on steam?
In addition to the other options here you could look at nw.js
-
Console Commands, Kill Count And Saving System
I don't think you can access it by default, but crosscode runs on [nw.js](https://nwjs.io). I know there is a way to get the chromium devtools to open, but I haven't been able to.
-
DuckieTV not launching
or browse the NWJS home page at https://nwjs.io/
- Notestation mac os client or trojan?
-
[AskJS] Are there any Electron alternatives that uses less recourses?
If windows is your target, you can use .hta If Ubuntu is your target, you can use GJS If Mac is your target - well you are going to use something like QT if you need total control or nwjs.io
-
Running Node Apps on BrightSign Devices
BrightSign has pretty good docs that explain this. There are a ton of similarities to running NW.js, so it might make sense to check that out as well (https://nwjs.io/). DM me if you have more questions. My team and I have built a few Node applications for BrightSign players.
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?
betaflight-configurator - Cross platform configuration tool for the Betaflight firmware
emotion - 👩🎤 CSS-in-JS library designed for high performance style composition
neutralinojs - Portable and lightweight cross-platform desktop application development framework
esbuild-plugin-solid
nodegui - A library for building cross-platform native desktop applications with Node.js and CSS 🚀. React NodeGui : https://react.nodegui.org and Vue NodeGui: https://vue.nodegui.org
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.
user-agent-desktop - Ghostery Desktop Browser
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
greenworks - a node.js plugin to integrate nw.js/electron games with steamworks
postcss-nested - PostCSS plugin to unwrap nested rules like how Sass does it.
sc-controller - User-mode driver and GTK3 based GUI for Steam Controller
@artsy/fresnel - An SSR compatible approach to CSS media query based responsive layouts for React.