ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Since Dart Sass 1.23, the @use rule loads stylesheets as namespaced modules, and Sass variables like $primary can be referenced through an alias such as t.$primary . The documented behavior for CSS custom properties is different: declarations like --primary are plain CSS rather than Sass variables, so they are not exposed through a module namespace and are n
A design goal is to recover from a failed Bulma upgrade without changing HTML markup. Two documented approaches are relevant for this constraint. One approach is to pin Bulma to a specific version in package.json or the CDN link and revert by reinstalling the previous version. The other approach is to rely on Bulma’s CSS custom properties introduced from ver
Bulma v1 documents two customization approaches: overriding Sass variables before compilation and overriding CSS custom properties at runtime. A project that needs both structural global changes and dynamic theme switching must decide how to divide responsibility between these layers. The unresolved behavior concerns the incomplete mapping between Sass varia
I'm designing the theming layer for a project built on Bulma and need to pick one customization strategy before the codebase grows. Bulma's documented approach is to override Sass variables such as $primary before importing the framework, which requires a Sass build step and produces a static compiled stylesheet. The complication is that parts of Bulma's out
sass
bulma