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
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

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 feature, 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.

1. Add funnel diagram type: This issue proposes adding a new funnel diagram type to Mermaid, aiming to support common business visualizations such as sales pipelines, product growth metrics, and customer support throughput. The user suggests multiple syntax options for defining funnel charts and expresses intent to implement the feature, while the community discusses aligning the syntax closely with existing Mermaid conventions to ensure consistency and ease of use.

   • The comments focus on refining the proposed syntax, with initial preference for the second example but later favoring the first for better alignment with existing diagram types and straightforward note association. The discussion culminates in a team-proposed syntax that integrates configuration options and styling within Mermaid’s established patterns, inviting further feedback before finalizing the implementation.
   • Number of comments this week: 3

Since there were fewer than 5 open issues, all of the open issues have been listed above.

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.

1. Tooltips for emoji in Diagram Syntax doc tree: This issue proposes adding tooltips to the emoji displayed next to the names of various diagram types in the "Diagram Syntax" section of the documentation tree. The goal is to help users understand the meaning of these icons, as currently there is no reference explaining their significance, which can lead to confusion even for experienced users.
2. log scale for xychart-beta: This issue proposes adding a scale string field to the xychart-beta component that defaults to linear but can also accept log as an option, enabling logarithmic scaling of charts. This enhancement aims to allow users to version control graph data with true values while displaying the data on a logarithmic scale, with potential for future extension to other scale types.
3. Unable to Style Sequence Diagram Title: This issue describes a problem where users are unable to change the font size of the title in sequence diagrams created with Mermaid, resulting in titles that appear very small and difficult to read. The reporter notes that while other diagram types in Mermaid support title styling attributes, such as font size, this functionality is not yet available for sequence diagrams, leading to a reliance on Markdown titles as a workaround.
4. SVG rendering formatting issues with markdown input: This issue addresses problems with SVG rendering when nodes in a Mermaid diagram contain markdown formatting, resulting in inconsistent visual output. Specifically, it highlights that opening the SVG in a new tab causes additional height to be added to the node, while downloading the SVG leads to text being cut off without adjusting the node height, causing formatting discrepancies.
5. Vite build error with mermaid version 10.9.0: This issue describes a build error encountered when using Mermaid version 10.9.0 in a Vue 3 and Vite application. While the Mermaid graphs render correctly during development, the application fails to start after building, producing a "TypeError: Cannot set properties of undefined (setting 'prototype')" related to Mermaid's API initialization.

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: 5

Summarized Issues:

• Diagram Annotation and Commenting: This topic covers the need for a universal comment or note syntax that can be attached to entities and visualized across all Mermaid diagram types, allowing annotations such as bugs or todos to be displayed directly within diagrams. This feature would enhance clarity and communication by embedding relevant notes within the visualizations.
• issues/7193

• Flowchart Node Formatting Issues: This topic addresses the problem of being unable to add manual line breaks to flowchart nodes containing mathematical equations in Mermaid diagrams, regardless of the placement of the breaks inside or outside the math expressions. This limitation restricts the readability and formatting flexibility of complex nodes.
• issues/7194

• New Diagram Types and Features: This topic involves proposals for new diagram types and features, including a funnel diagram for visualizing sales pipelines and customer support throughput, and a Milestone Timeline feature for displaying project milestones inline on Gantt charts. These additions aim to expand Mermaid's capabilities for business and project management visualizations.
• issues/7195, issues/7199

• Block Diagram Layout Constraints: This topic highlights the issue in Mermaid's block diagrams where subblocks are forced to share the same maximum height, preventing automatic adjustment based on individual content size. This constraint limits the flexibility and visual accuracy of block diagrams.
• issues/7198

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:

• Diagram Rendering Errors: Several issues highlight problems with diagram rendering due to code or styling errors. One issue involves duplicate IDs in block diagrams causing lines not to display, while another concerns ineffective border removal in treemap-beta diagrams despite correct style usage, both leading to incorrect visual outputs.
• [issues/7159, issues/7167]

• Documentation Code Errors: Errors in example code within documentation cause parsing failures and confusion. Specifically, a trailing comma in the radar diagram example leads to a parse error, necessitating correction to ensure proper parsing and accurate documentation.
• [issues/7187]

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: 4

Key Open Pull Requests

1. Claude/add sandbox base url 01 h hj4v fa3 g qc ug p cs jd qe9 t: This pull request introduces a new sandboxBaseUrl configuration option that enables the resolution of relative URLs to absolute URLs within sandboxed iframes when using securityLevel: 'sandbox', thereby preserving link functionality inside data URI-rendered diagrams without compromising sandbox isolation or security.

• URL: pull/7203

• Merged: No

• Associated Commits: ff41e, de2fb, fd501, 9b5e4, f77b8, 5b49a, 496ac

2. fix(architecture): expand group bounding box to include child sizes (fix #7175): This pull request fixes issue #7175 by modifying the calculation of group bounding boxes in architecture diagrams to expand correctly based on the rendered sizes of child elements plus padding, ensuring group boxes no longer overlap or fail to encompass wide children or long group names.

• URL: pull/7190

• Merged: No

• Associated Commits: abe31, 451fc, ba342, 5c9e8

3. Bug/fix gantt value valid: This pull request addresses a bug in the Gantt chart feature by fixing the todayScale value to prevent it from being NaN by ensuring it is at least zero.

• URL: pull/7196

• Merged: No

• Associated Commits: 4da0b, ccc24, 89c4f, e5ca0

Other Open Pull Requests

• KaTeX Math Equation Rendering Fixes: This pull request resolves the issue where newlines were not rendered in flowchart nodes containing KaTeX math equations by updating the markdown processing logic. It ensures that newline characters are correctly converted into <br/> tags, allowing proper display of newlines in both plain text and markdown-formatted nodes with math content.
• pull/7202

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: 5

Key Closed Pull Requests

1. 5496 : fixed UI crash from excessive tick generation with invalid dates/intervals: This pull request fixes a critical bug in the Mermaid Gantt chart rendering where invalid dates or excessively small tick intervals caused infinite loops and UI crashes by addressing Temporal Dead Zone errors and adding validation to prevent excessive tick generation, thereby improving stability and error handling.

• URL: pull/7197

• Merged: 2025-11-27T17:19:25Z

• Associated Commits: 6025e, 45423, 88fd1, 8bfd4, bf50c, 0843a, 87c56, ac5fd, 88e8a, 73b86, b115a

2. docs(block): correct block arrow example: This pull request corrects the block arrow example in the documentation by fixing an issue where using the same ID caused the previous arrow to be overridden, thereby addressing the problem reported in issue #7159.

• URL: pull/7172

• Merged: 2025-11-25T07:09:04Z

• Associated Commits: 9df18, 6e869

3. 7167 : fix classDef style application for treemap diagramtype: This pull request fixes the application of user-defined classDef styles in treemap diagrams by resolving type inconsistencies and SVG attribute override issues, ensuring that custom styles are correctly applied and consistent with other diagram types like flowchart and state diagrams.

• URL: pull/7178

• Merged: 2025-11-27T08:57:54Z

• Associated Commits: bf7c5, 96ca7

Other Closed Pull Requests

• Documentation Fixes: These pull requests address errors in the Mermaid documentation and UI stability issues. One fixes a parse error by removing a trailing comma in the radar diagram example, while another merges a fix that prevents a UI crash caused by excessive tick generation in the Gantt chart component due to invalid dates or intervals.
• pull/7188, pull/7200

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.