Skip to content

Fix design token syntax issues and upgrade to Style Dictionary 5 - #1395

Open
richadr wants to merge 19 commits into
mainfrom
build/test-command-exit-1
Open

Fix design token syntax issues and upgrade to Style Dictionary 5#1395
richadr wants to merge 19 commits into
mainfrom
build/test-command-exit-1

Conversation

@richadr

@richadr richadr commented Apr 9, 2026

Copy link
Copy Markdown
Member

Currently, pnpm test outputs a list of issues, but the pipeline is not blocked by them. By changing the package.json command, the pipeline will now fail if there is an issue.

So that surfaces a couple of issues, which are also fixed in this PR.

  1. In some cases, a color was improperly referenced, and fixing it required choosing a color shade. In this case I opted for the most default one, e.g.:
-        "border-color": { "value": "{buren.color.feedback-danger}" },
+        "border-color": { "value": "{buren.color.feedback-danger.50}" },
  1. Some tokens were not referenced correctly (for example missing braces)

  2. There was a very hard to find ordering bug that was supposedly fixed in Style Dictionary 4.1.2 but properly fixed in 5.1.1 (issue). Upgrading fixes values being referenced before they are declared. So this requires a major upgrade of Style Dictionary.

  3. In Style Dictionary 5, referencing with .value suffix is no longer allowed, this has been removed where needed. The SD5 upgrade was done across the board, and will minor-bump every *-design-tokens package. Other breaking changes are not relevant for us.

@richadr
richadr requested a review from a team as a code owner April 9, 2026 14:07
@vercel

vercel Bot commented Apr 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
themes Ready Ready Preview Aug 12, 2026 8:07am

Request Review

@sonarqubecloud

Copy link
Copy Markdown

Robbert
Robbert previously approved these changes Jul 16, 2026
@Robbert
Robbert self-requested a review July 16, 2026 16:11
@richadr
richadr marked this pull request as draft July 21, 2026 10:06
@Robbert
Robbert removed their request for review August 10, 2026 15:27
@sonarqubecloud

Copy link
Copy Markdown

@richadr richadr changed the title build: fail the test command if it fails Fix design token syntax issues and upgrade to Style Dictionary 5 Aug 12, 2026
@codecov-commenter

codecov-commenter commented Aug 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.51%. Comparing base (0d5b29f) to head (25f89c8).
⚠️ Report is 49 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1395   +/-   ##
=======================================
  Coverage   89.51%   89.51%           
=======================================
  Files          19       19           
  Lines        1392     1392           
  Branches      185      174   -11     
=======================================
  Hits         1246     1246           
  Misses        145      145           
  Partials        1        1           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@richadr
richadr marked this pull request as ready for review August 12, 2026 08:12
@richadr
richadr requested review from a team as code owners August 12, 2026 08:12
@richadr
richadr requested a review from Robbert August 12, 2026 09:32
Comment thread package.json
"test": "npm-run-all test-workspaces test-build:**",
"test-build:css": "find proprietary/*/dist -type d \\( -name node_modules \\) -prune -false -o -name '*.css' -print0 -exec sass --no-source-map {}:/dev/null \\;",
"test-build:scss": "find proprietary/*/dist -type d \\( -name node_modules \\) -prune -false -o -name '*.scss' -print0 -exec sass --no-source-map {} \\;",
"test": "pnpm run test-workspaces && pnpm run test-build:css && pnpm run test-build:scss",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

De bedoeling van pnpm run test-build is om juist separate te zijn van pnpm run test.

Ik denk dat we dit ergens in het handboek moeten gaan documenteren, als we dat niet al hebben.

  • pnpm run test: draai alle test die mogelijk zijn zonder te wachten op pnpm run build, voor snelle feedback in CI
  • pnpm run test-build: draai alle test die pas mogelijk zijn ná pnpm run build

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hoe zeker weten we dat het een minor is en niet major?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants