fix(architecture): floor service label width at 90px to prevent mid-word wrap

[txmxthy]

📑 Summary

Floors the architecture-beta service label width at 90px so long single-word labels (e.g. ClickHouse) no longer wrap mid-character at small iconSize values. Multi-word labels still wrap at word boundaries.

Symptom (at iconSize: 50):

Before	After
ClickHouse rendered as ClickHous / e (character-boundary wrap)	ClickHouse renders on a single line

This is the visible part of a complaint about uneven-looking rows in architecture-beta diagrams at small icon sizes — the icons are actually pixel-aligned, but a mid-character wrap on one node makes the whole row look misaligned.

📏 Design Decisions

createText is called with width: iconSize * 1.5. At iconSize: 50 that's 75px, too narrow for the 10-char word "ClickHouse" at the default font size, so the text engine wraps at the next available character boundary.

Raising the floor to 90px:

• preserves the existing iconSize * 1.5 scaling above the floor (iconSize >= 60) — for the default iconSize: 80 (120px label area) this is a no-op;
• only kicks in below 60px, where the previous width was producing visibly broken mid-character wraps;
• does not change cytoscape's node bounding box (still iconSize × iconSize), so layout positioning is unaffected.

I considered fully decoupling label width from iconSize (e.g. always 90px) but kept the existing scaling above the floor to avoid regression for users who tuned iconSize upward.

📋 Tasks

• 📖 have read the contribution guidelines
• 💻 unit/e2e tests — relying on existing architecture Cypress visual coverage; happy to add a dedicated imgSnapshotTest at small iconSize if reviewers prefer.
• 📓 docs — N/A (internal rendering fix, no new user-facing API).
• 🦋 changeset added — .changeset/fix-architecture-label-width-floor.md (patch).

Notes for the reviewer

• Pre-commit hook (pnpm --filter mermaid run docs:build invoked by lint-staged) currently fails on develop itself because of pre-existing TypeScript errors in packages/mermaid/src/diagrams/wardley/wardleyParser.ts. Hook bypassed for this PR; this PR does not touch any docs file, so the docs:build failure is not caused by this change. Worth filing/fixing separately.
• Companion PRs in this stack (independent of this fix):
  • feat(architecture): expose fcose layout knobs via config #7707 — expose fcose layout knobs via config (Resolves non-deterministic architecture-beta rendering #6024).
  • feat(architecture): add 'align row|column' directive for declarative layout #7708 — align row|column directive for declarative architecture-beta layout (Resolves Feat for architecture-beta, flexbox like layout #6817).

[changeset-bot]

🦋 Changeset detected

Latest commit: aadf9c9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
mermaid	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[netlify]

✅ Deploy Preview for mermaid-js ready!

Name	Link
🔨 Latest commit	aadf9c9
🔍 Latest deploy log	https://app.netlify.com/projects/mermaid-js/deploys/6a0add13ca26f000081460e3
😎 Deploy Preview	https://deploy-preview-7706--mermaid-js.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[pkg-pr-new]

Open in StackBlitz

@mermaid-js/examples

npm i https://pkg.pr.new/@mermaid-js/examples@7706

mermaid

npm i https://pkg.pr.new/mermaid@7706

@mermaid-js/layout-elk

npm i https://pkg.pr.new/@mermaid-js/layout-elk@7706

@mermaid-js/layout-tidy-tree

npm i https://pkg.pr.new/@mermaid-js/layout-tidy-tree@7706

@mermaid-js/mermaid-zenuml

npm i https://pkg.pr.new/@mermaid-js/mermaid-zenuml@7706

@mermaid-js/parser

npm i https://pkg.pr.new/@mermaid-js/parser@7706

@mermaid-js/tiny

npm i https://pkg.pr.new/@mermaid-js/tiny@7706

commit: aadf9c9

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 3.27%. Comparing base (2a51ae4) to head (aadf9c9).

Files with missing lines	Patch %	Lines
...kages/mermaid/src/diagrams/architecture/svgDraw.ts	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #7706   +/-   ##
=======================================
  Coverage     3.27%   3.27%           
=======================================
  Files          600     600           
  Lines        60657   60657           
  Branches       916     916           
=======================================
  Hits          1985    1985           
  Misses       58672   58672           

Flag	Coverage Δ
unit	3.27% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...kages/mermaid/src/diagrams/architecture/svgDraw.ts	0.32% <0.00%> (ø)

🚀 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.

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	⚠️ Changes detected (Review)	1 added	May 18, 2026, 9:38 AM

[pbrolin47]

Hi @txmxthy,
Thanks for this. Just on thing to address

What's Working Well

🎉 [praise] Surgical and precise fix. Math.max(iconSize * 1.5, 90) is one line that addresses the symptom exactly. The node bounding box (iconSize × iconSize) is correctly left untouched, so layout
positioning is unaffected — this is a purely visual fix.

🎉 [praise] Clear design rationale in the PR body. The explanation of why 90 was chosen (breakeven at iconSize: 60, no-op at default iconSize: 80), and the explicit decision to keep the scaling
above the floor rather than fully decoupling, is exactly the kind of documentation that helps future maintainers.

---

Things to Address

🔴 [blocking] As you mentioned in the PR body, I think a visual test for small iconSize shall be added. Thanks in advance

---

[txmxthy]

Thanks @pbrolin47 — added the requested visual regression test in 092011f0b.

The new imgSnapshotTest exercises iconSize: 50 with three single-word service labels ("ClickHouse", "Postgres", "MessageBroker"). At the historical label-area width of iconSize * 1.5 = 75px, those labels would wrap mid-character; with the 90px floor they should stay on one line. The diagram itself is intentionally minimal so the snapshot focuses on label rendering rather than layout.

[pbrolin47]

@txmxthy Thanks for adding the visual-test. In the new test, is the rendered output as expected?? Based on the description "At the historical label-area width of iconSize * 1.5 = 75px, those labels would wrap mid-character; with the 90px floor they should stay on one line.", I kind of expected the label to stay on one line, but some labels are wrapped mid-character.

[txmxthy]

Sorry you are right with that icon size it was still having issues.

Looks a bit better? the scaling and zoom is annoying with canvas, it makes the font look larger for the iconsize 30 example

[txmxthy]

I believe its a difference with the headless chrome font size vs my dev environment -- not sure what the best course of action is here for fixing it.

Do you have a preference for label size that should be supported by default?

The cypress test uses iconSize: 50 with three labels: ClickHouse (10 chars), Postgres (8 chars), MessageBroker (13 chars). With the 120px floor:

Could raise the floor but that would no longer strictly be a no-op at the default iconSize: 80

Could shorten the label on that worst case test and set the threshold at ~12 letters for default single-word labels?

Any other ideas?