ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #stylus
Learn why a Stylus mixin may skip its body when optional arguments are omitted and how to fix missing CSS output.
Learn how Stylus silent mixins let you define reusable style blocks that only appear in the compiled CSS when called, reducing bloat while keeping your stylesheets maintainable.
Learn how to create, import, and use Stylus mixins for reusable CSS patterns, parameterized styles, and vendor‑prefix handling. Follow a step‑by‑step guide to reduce duplication, keep output lean, and maintain a modular stylesheet architecture.
Learn how to use Stylus transparent mixins to create clean, reusable CSS patterns without the syntactic noise of traditional preprocessors.
When adjusting colors in Stylus, built‑in functions are quick and reliable for simple tweaks, while custom functions offer flexibility for advanced color math. This guide compares the two, highlights trade‑offs, and shows a hands‑on example.
We maintain a Stylus-based component library where dozens of modules reference the same variables-and-mixins partial. The build compiles everything into one stylesheet through the Stylus CLI, and I need to pick a single inclusion convention for these shared dependencies. My understanding is that @import inlines the target file at every reference point, while
In a Stylus codebase with many partials that all depend on a shared library of mixins and variables, I need to pick a consistent inclusion strategy. Stylus documents two directives: @import inlines the target file on every reference, while @require includes a given file only once per compilation. The concrete constraint is stylesheet size: the shared file is
After upgrading the Stylus CLI, invoking stylus on an existing stylesheet fails with Error: Cannot find module , which appears to be a native binding or binary mismatch between the newly installed version and the current Node runtime. The goal is to get a working compiler back without disturbing other projects that may share the same global installation. The