Sass @use vs @import: Namespace Safety for Style Modules
Stop silent variable collisions in large Sass stylesheets by migrating from @import to namespaced @use modules.
Loading…
ReadMeFeed / Community knowledge
#css-modules
Real questions. Useful conversations. Find the people who know your stack.
Modern Sass Architecture with @use and Built‑in Modules
Learn how Sass’s @use rule eliminates duplicate output and global namespace clashes by loading modules once under an explicit namespace, with a concrete migration example and verification steps.
sassIntegrating Devicon into a React Project: A Practical Guide
Learn how to add Devicon icons to a React app using npm, CSS modules, and a small component that lists languages. Compare icon font vs SVG, and see how to verify the setup.
reactChoosing Vite's Native CSS Modules vs. PostCSS‑Based Modules: A Practical Decision Guide
When adding scoped styles to a Vite project, choose between Vite’s built‑in CSS modules and a PostCSS‑based solution. This guide compares build size, workflow, browser support, and feature richness, then shows concrete config examples and validation steps.
vite
postcssReplace Sass @import with @use and @forward in Dart Sass
Migrate Dart Sass stylesheets from deprecated @import to the @use/@forward module system without duplicating CSS or breaking global tokens.
Using Sass @use with Namespaces for Modular Stylesheets
Learn how the Sass @use rule loads a module once, scopes its members under a namespace, and prevents duplicate CSS output—key for scalable stylesheet architecture.
Vite.js Built‑In CSS Modules: Enable, Use, and Avoid Common Pitfalls
Learn how Vite automatically treats files ending in .module.css (and variants) as CSS Modules, how to import them, tweak the hash format, and what to watch out for when mixing global and module styles.
vitejsCSS syntax error halts Next.js build amid unresolved next/image loader validation
In Next.js 13.x, a CSS module with invalid syntax causes the `next build` command to fail, emitting a webpack‑css-loader error that points to the offending file and line number. Concurrently, an open discussion exists about whether the `next/image` loader prop should enforce remote‑image domain validation at build time, and no final decision has been made. T
nextjsStylus source maps and CSS Modules class hashing in Vite
Integration boundary Stylus compiles to CSS with source maps enabled, while Vite's CSS Modules implementation hashes class names during the transform pipeline. The Stylus compiler emits a source map that references original .styl line numbers, but the final class identifiers in the browser are hashed tokens produced by Vite's postcss-modules step. Unresolved
stylus