palantir/blueprint

Unable to override default colors (e.g. `$blue2`) with node-sass or dart-sass in v4

Open

#5297 opened on May 11, 2022

View on GitHub
 (19 comments) (1 reaction) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
Domain: APIDomain: toolingP1Package: corehelp wanted

Description

After upgrade to v4 I am unable to override default colors (e.g. $blue2), even using node-sass. Has anything changed from v3 which would impact this?

Originally posted by @dylangrandmont in https://github.com/palantir/blueprint/issues/4759#issuecomment-1080979948

Contributor guide

Tech stack
typescriptreactcss
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Knowledge of Blueprint v3 themingExperience with Sass variable overridesFamiliarity with node sass or dart sass
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the regression from v3 to v4 in Blueprint's theming system. Look at the migration guide and changelog for any changes related to Sass variable overrides. Examine the source files where colors like $blue2 are defined, possibly in `src/blueprint.scss` or similar. Review the linked comment in issue #4759 and any related PRs to understand if the color system was intentionally changed. Test locally with a sample app to confirm the override behavior and identify the root cause.