Sass Variable Override Limitations in Production Build Pipelines

Customization via Sass Variables

Bulma relies on a Sass-based architecture where user-defined variables must be declared before the core framework import so overrides take effect. This customization happens at compile time, so redefining the primary color palette or spacing scale requires a rebuild rather than a runtime change.

Production Build Constraints

When moving from local development to a production pipeline, minification and CSS optimization steps are introduced. There is uncertainty about how aggressive minifiers or purging tools interact with Bulma's compiled output, particularly when CSS custom properties are used alongside Sass-compiled variables, and whether browser-target configurations affect which custom properties survive the build.

• Does the required Sass import order for overrides behave consistently across different build tool configurations?
• Can production minification settings strip the CSS custom properties that some Bulma components rely on?
• What is a reliable way to verify that overrides survived the production build?