ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #stylus
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.
When developing a Stylus stylesheet that splits logic across multiple files, the @import directive is used to pull in external modules. The goal is to ensure that any mistyped or missing import path is surfaced during compilation so that omitted styles do not go unnoticed. In practice, the Stylus compiler appears to proceed without emitting a warning or erro
Stylus @require deduplication with multiple path forms The goal is to compile a Stylus entry that includes the same partial twice using @require, once through a relative path and once through an absolute path or symlink. Documented behavior states that @require includes a target file only once per compilation, based on the resolved file path. It is unclear w
Stylus @import inlining with filename and paths options The goal is to compile a Stylus entry file with @import directives so nested variables and mixins are inlined into the rendered CSS. Compilation should resolve imports only from a temporary fixture directory and must not require production credentials. Stylus has no built-in filesystem sandbox, so impor
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
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
Goal Migrate a small application's Stylus stylesheets from legacy = mixin syntax to Stylus 1.x without service interruption while keeping compiled CSS output stable. Constraints Stylus 0.x and 1.x handle variable interpolation differently, and the newer --compress flag may drop mixins defined with the legacy = sign syntax. It is unclear whether existing = mi
Goal: make Stylus @import resolution behave the same in local development and production builds without depending on the compiler's current working directory. Stylus resolves imports by checking the current directory first, then directories supplied with --paths . Local setups often appear to resolve node_modules imports implicitly through symlinks or filesy
vite