ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Determine how variable precedence behaves when transitioning from legacy global imports to the new module system in Stylus 3.0, especially around ambiguous names and nested overrides. Constraints Global variables are still widely used in existing codebases. The module system introduces namespaced imports that aim to prevent namespace pollution. Omitting
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
I'm structuring a design-token layer in Stylus (current stable release) and need to pick one strategy before the codebase grows. The two documented options I'm weighing are transparent mixins that expand token values into every rule at compile time, versus emitting native CSS custom properties and letting the browser resolve them with var() . The concrete co
Less employs a lazy-loading evaluation strategy that permits variables to be referenced before their formal definition in certain contexts. This behavior is typically reliable for global variables defined later in the same compilation pass. Complexity arises when combining lazy-loading with hierarchical scoping. When a variable is used within a nested select
Less employs a lazy-loading variable system where variables are evaluated at the time of use rather than at the point of declaration. This behavior is intended to allow variables to be defined after they are referenced in certain contexts. When utilizing nested mixins that rely on local variable overrides within specific CSS selectors, there is uncertainty r
Variable Scope and Evaluation Order In Less, variables are lazily evaluated, meaning their values are resolved at the point of use rather than at the point of declaration. This behavior allows a rule to reference a variable that is defined later in the same scope. When a variable is declared multiple times within a single scope, the last definition typically
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
Migration context A team is incrementally migrating a legacy Sass codebase to Stylus 0.64 while maintaining zero-downtime deployments. Existing component files contain raw CSS snippets that rely on Sass variables and nested selector structures. The goal is to embed these snippets in Stylus files without rewriting selector hierarchies or losing variable refer
Stylus supports mixins for reusable groups of declarations, with optional arguments for dynamic generation. The compiler expands mixins at build time, so each call is inlined into the output. The design goal is to understand the trade-off between source convenience and final CSS size when mixins are reused across selectors. Silent mixins provide logic-only a
stylus
less