Weekly GitHub Report for Mermaid: March 09, 2026 - March 16, 2026 (19:44:52)
Weekly GitHub Report for Mermaid
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is @mermaid-js/parser@0.4.0
1.2 Version Information:
On March 25, 2025, a minor update was released that introduced the addition of a Radar Chart, enhancing the charting capabilities of the platform. This update reflects ongoing efforts to expand visualization options.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
[TYPE: BUG / ERROR] [TYPE: OTHER] [STATUS: APPROVED]
themeVariables : fontSizehas no effect in a Gantt diagram: This issue reports that setting thefontSizeproperty withinthemeVariablesdoes not affect the font size in a Gantt diagram, making it impossible to adjust text size as expected. The user suggests that font size adjustments should also scale bar heights and spacing appropriately to maintain visual consistency in the diagram.- The comments clarify that font size can be configured using
gantt.fontSizeandgantt.sectionFontSizesettings, but note that other diagram elements do not scale accordingly, causing visual issues. Users appreciate the workaround and suggest updating the documentation to reflect this configuration method, while maintainers agree that both respectingthemeVariables.fontSizeand proportional scaling of diagram elements need to be fixed. - Number of comments this week: 4
- The comments clarify that font size can be configured using
-
[TYPE: BUG / ERROR] [STATUS: TRIAGE] Fix: Syntax error in class diagrams with nested generics and inline type definitions: This issue addresses a syntax error in the Mermaid class diagram renderer that occurs when defining classes with nested generic types and inline type definitions, which causes the parser to confuse nested generic closings with markdown strike-through tokens, leading to rendering failures. The problem is demonstrated in the classchart.html demo file and is resolved by modifying the class definitions to use block syntax, adding whitespace between nested tildes, and correcting method return type syntax to comply with the parser's stricter requirements.
- The comments reveal a user volunteering to fix the syntax error, followed by confirmation that a fix was already implemented and a pull request submitted shortly after the issue was reported.
- Number of comments this week: 2
-
[TYPE: BUG / ERROR] [STATUS: TRIAGE] Graph vs. Flowchart: Different Colors and Layout for Identical Diagrams: This issue reports that rendering identical diagrams using
graph LRandflowchart LRin Mermaid.js results in unexpected visual differences, specifically in node fill colors and vertical layout spacing, despiteflowchartbeing a newer alias forgraphthat should produce identical output. The user provides detailed reproduction steps, code samples, screenshots, and suggests potential fixes involving CSS vendor prefixes, consistent theming, and browser-specific rendering normalization to address the discrepancy observed primarily in Microsoft Edge and Chrome browsers.- The comments confirm the bug is reproducible locally on multiple browsers and likely stems from differences in the rendering code between
flowRenderer.jsandflowRenderer-v2.js; the issue remains unresolved after an accidental reopen/close action. - Number of comments this week: 2
- The comments confirm the bug is reproducible locally on multiple browsers and likely stems from differences in the rendering code between
-
[TYPE: BUG / ERROR] [STATUS: TRIAGE] Can't run "run" script despite following setup docs: This issue describes a problem where the user is unable to run the "run" script as documented because the Docker build process fails with a "Cannot find matching keyid" error related to corepack and Node.js. The user is seeking guidance or a workaround since the documentation does not address this error, and a suggested fix involves updating the Node base image or modifying the Dockerfile, but the user is unsure how to proceed given the immutability of the specified node image.
- The comment explains that the error can be resolved by bumping the Node base image version and updating the git version in the Dockerfile, and also mentions node-gyp installation issues that require adding python to the container; it suggests using a specific commit as a temporary workaround and recommends upgrading to a newer Node version for long-term stability, while noting that production fixes might involve multi-stage Docker builds.
- Number of comments this week: 1
-
[TYPE: BUG / ERROR] [STATUS: TRIAGE] Prevent arrows to cross each other: This issue is about a user experiencing unreadable diagrams in Mermaid due to arrows crossing each other unnecessarily in a graph containing subgraphs. The user seeks advice on how to prevent these arrow crossings to improve diagram clarity.
- The comment explains that the problem is related to the combination of layout with subgraphs and edge ordering, suggesting that declaring certain edges before the subgraph can resolve the arrow crossing issue, and provides an updated code example demonstrating this solution.
- Number of comments this week: 1
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
As of our latest update, there are no stale issues for the project this week.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 10
Summarized Issues:
- Rendering and Layout Issues: Several issues report problems with diagram rendering and layout inconsistencies, including incorrect font size scaling in Gantt diagrams, swapped subgraph directions in flowcharts, unexpected visual differences between
graph LRandflowchart LR, and multiple rendering problems in C4 container diagrams such as overlapping labels and text overflow. These issues cause diagrams to display incorrectly or inconsistently, impacting readability and user experience. - issues/7471, issues/7477, issues/7486, issues/7492
- Parsing and Syntax Errors: There are parsing failures and syntax errors affecting Mermaid's diagram rendering, including problems with nested generic types in class diagrams, and parsing errors in ER diagrams when using certain relationship notations. These errors lead to rendering failures, crashes, or inability to parse valid diagram syntax.
- issues/7480, issues/7482
- Diagram Symbol and Color Issues: Some issues highlight problems with unclear or incorrect diagram symbols and color assignments, such as non-standard cardinality symbols in ER diagrams and incorrect color rendering for the first person node in C4 context diagrams. These issues reduce diagram clarity and cause confusion in interpretation.
- issues/7475, issues/7491
- Diagram Readability Improvements: One issue focuses on improving diagram readability by preventing unnecessary arrow crossings, which can make diagrams easier to understand and visually cleaner.
- issues/7496
- Build and Setup Failures: There is a reported failure in running the documented "run" script due to a Docker build error related to corepack and node image verification, preventing users from successfully building or running the project as expected.
- issues/7476
2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.
Issues Closed This Week: 3
Summarized Issues:
- Rendering and Visual Hierarchy Issues: The rendering of Ishikawa diagrams breaks when indenting the effect statement more than its causes, causing incorrect visual hierarchy due to nesting subcauses failing. Additionally, the quadrant chart demo page shows multiple visual inconsistencies such as label color mismatches, missing background fills, and alignment problems when resizing in Microsoft Edge.
- issues/7469, issues/7487
- Parsing Errors in Diagram Syntax: Mermaid version 11.13.0 throws a parsing error when using the identifier
1on the right side of a relationship in ER diagrams because1was previously reserved as a cardinality alias. This causes the parser to fail when encountering this syntax, breaking diagram generation. - issues/7472
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 6
Key Open Pull Requests
1. feat: add support for inline markdown links in text rendering: This pull request adds support for rendering inline Markdown links within text, including sequence diagram messages, actor descriptions, and flowchart nodes and edges, enhancing the text rendering capabilities of the Mermaid project.
- URL: pull/7470
- Associated Commits: acab5, 3a09d, bd6f5, 91ab2, 5db81, c6633, a2326, 9cb55, 3b128, afbf4, d134a, 448ae, 7225c, 04b03, 4550a, d0aaa
2. bug/7477_fix_subgraph_direction: This pull request fixes the issue where subgraph direction in flowcharts was not honored correctly by ensuring that the specified direction (top-to-bottom or left-to-right) is respected, introduces heuristics for handling unlinked clusters to display the expected orientation, and includes multiple improvements and error handling enhancements in cluster layout processing to prevent crashes and improve rendering robustness.
- URL: pull/7479
3. fix: resolve syntax errors in classchart demo: This pull request fixes syntax errors in the classchart demo by modifying the parser to correctly handle nested generic types using bracketed notation and space-separated generic closing tokens, thereby preventing misinterpretation of the closing tildes as Markdown strike-through syntax.
- URL: pull/7481
Other Open Pull Requests
- Documentation fixes: This topic includes pull requests that improve the accuracy and clarity of documentation. One pull request fixes the arrowhead syntax in the sequenceDiagram.md file to enhance understanding.
- pull/7485
- Diagram layout improvements: These pull requests address layout issues in state diagrams by properly applying spacing configuration values to the Dagre layout engine. They ensure compatibility with both legacy and v2 renderers, use safe default and clamped spacing values, and maintain correct rendering of nested states and loops.
- pull/7490
- Configuration linting automation: This pull request adds a GitHub Action to lint the renovate.json configuration file. It prevents broken renovate config changes from being merged by addressing the limitation that the @renovatebot App's automatic checks do not run on pull requests from forks.
- pull/7495
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 14
Key Closed Pull Requests
1. feature/2645: add TreeView Diagram : This pull request finalizes the addition of the TreeView diagram feature by addressing parser bugs related to titles and accessibility, adding tests for the Langium parser, updating examples and demos with modern formatting, resolving merge conflicts, and enhancing documentation and integration tests.
- URL: pull/7396
- Associated Commits: 3b398, 99dde, bd824, f7ebf, 18f20, 99406, 85914, 7bae2, 353a2, 34f80, c1ec5, c8c66, 48ea9, 4135f, caf34, 387ba, a2acd, c6139, 4947e, 781da, 613e1, adf46, 4aa70, 251d4, 20939, fa86f, a5255, 0cfe0, b8519, 209d2, ae680, c11c2, ec4cc, 6eb0e, 293b3, b0752
- Associated Commits: 3b398, 99dde, bd824, f7ebf, 18f20, 99406, 85914, 7bae2, 353a2, 34f80, c1ec5, c8c66, 48ea9, 4135f, caf34, 387ba, a2acd, c6139, 4947e, 781da, 613e1, adf46, 4aa70, 251d4, 20939, fa86f, a5255, 0cfe0, b8519, 209d2, ae680, c11c2, ec4cc, 6eb0e, 293b3, b0752
2. Bug/5741 fix duplicate svg element ids: This pull request fixes the issue of duplicate SVG element IDs across multiple Mermaid diagrams on the same page by extending the existing namespacing approach to prefix all internally generated SVG element IDs with their diagram’s unique SVG container ID, thereby preventing ID collisions that caused broken event bindings, missing arrow markers, and corrupted styling, and includes comprehensive tests and updates to rendering, CSS selectors, and event handlers to support this change.
- URL: pull/7410
- Associated Commits: 0fe25, 0f281, c2a2b, d2205, 72455, 2773d, c41bf, 10002, f0b57, ee5e9, 9beed, 04e43, f43a6, b8ab2, e5d07, 52559, 69800, 291fe, e0b67, 8f478, 98636, 3142c, 7fb25, 28733, 58b58, 79a19, 36a9e, 9090c, b632b, 1c371, 14a60, 1326f, 107ed, 15012
- Associated Commits: 0fe25, 0f281, c2a2b, d2205, 72455, 2773d, c41bf, 10002, f0b57, ee5e9, 9beed, 04e43, f43a6, b8ab2, e5d07, 52559, 69800, 291fe, e0b67, 8f478, 98636, 3142c, 7fb25, 28733, 58b58, 79a19, 36a9e, 9090c, b632b, 1c371, 14a60, 1326f, 107ed, 15012
3. draft: showDataLabelOutsideBar option for xy chart: This pull request introduces a new option, showDataLabelOutsideBar, for XY charts in Mermaid to allow displaying data values outside the bars on both vertical and horizontal bar charts, addressing user requests and improving data label visibility beyond the previous limitation of showing values only inside the bars.
- URL: pull/7382
Other Closed Pull Requests
- Documentation improvements and clarifications: Multiple pull requests enhance documentation by removing incorrect examples, adding detailed valid token formats for Gantt charts, and updating sidebar syntax to include new diagrams. These changes improve user guidance and ensure documentation accuracy across different features.
- pull/7442, pull/7443, pull/7460
- Renovate configuration fixes: Two pull requests correct typos in the Renovate configuration, fixing manager names and property keys to resolve invalid configuration errors. These fixes address issues #7484 and #7451 without requiring public-facing changes.
- pull/7488, pull/7483
- Parser and syntax error fixes: Several pull requests fix parsing errors and syntax issues in Mermaid diagrams, including ER diagram lexer tokenization, class diagram nested generics syntax, and flowchart style statement warnings. These improvements enhance parsing accuracy and user feedback while maintaining backward compatibility.
- pull/7473, pull/7489, pull/7441
- Feature enhancements and integrations: Pull requests introduce theme support for dataLabelColor in xy charts and add IntelliJ IDEA integration with the Mermaid Visualizer plugin. These updates expand customization options and integration capabilities for users.
- pull/7461, pull/7464
- Rendering fixes: One pull request fixes requirement edge label rendering by reverting to the original notation to prevent incorrect escaping when htmlLabels is false. This ensures correct visual output for requirement edges.
- pull/7445
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| lee-treehouse | 37 | 5 | 0 | 2 |
| claude | 28 | 0 | 0 | 0 |
| aloisklink | 24 | 2 | 0 | 0 |
| ashishjain0512 | 17 | 6 | 0 | 0 |
| knsv | 20 | 0 | 0 | 2 |
| taoqf | 15 | 1 | 0 | 0 |
| darshanr0107 | 14 | 1 | 0 | 0 |
| omkarht | 8 | 3 | 0 | 0 |
| sidharthv96 | 9 | 0 | 0 | 0 |
| awwaiid | 7 | 1 | 0 | 0 |