Weekly Project News

Archives
Subscribe
November 24, 2025

Weekly GitHub Report for Mermaid: November 17, 2025 - November 24, 2025 (12:05:42)

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, 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. Hard-coded styles in SVGs: This issue addresses the problem of hard-coded styles within SVGs generated by Mermaid, which complicates theme switching between dark and light modes. The reporter highlights that some diagram styles are embedded directly in the SVG elements rather than being controlled via CSS, causing readability issues when mixing SVG themes with different CSS themes, and suggests replacing these hard-coded styles with CSS for better flexibility.

    • The comments confirm that submitting a pull request to fix the issue is welcomed, with a reminder to ensure compatibility with the "rough" rendering style; the reporter seeks clarification on this point before proceeding.
    • Number of comments this week: 2

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 reports a problem with the Mermaid sequence diagram feature where users are unable to change the font size of the diagram title, resulting in titles that appear very small and difficult to read. The user notes that while other Mermaid graph types support title styling attributes, such as those in QuadrantChartConfig, similar 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 diagram use markdown formatting, resulting in inconsistent visual output such as added height or text being cut off in the SVG files. Specifically, these formatting issues occur when opening the SVG in a new tab or downloading it from the editor, causing discrepancies between the expected and actual appearance of the diagram elements.
  5. Vite build error with mermaid version 10.9.0: This issue describes a problem encountered when building a Vue 3 and Vite application that uses Mermaid version 10.9.0 to render graphs. While the development server runs without errors, the build process fails on application startup with a TypeError related to setting a property on an undefined object, preventing the Mermaid graphs from rendering correctly.

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

Summarized Issues:

  • Treemap rendering and styling issues: Multiple problems affect the treemap-beta diagrams, including hidden or unreadable labels inside nested child blocks and ineffective removal of borders from specific sub-blocks despite correct styling attempts. Additionally, sub-block fill colors are incorrectly blended with parent container colors, causing inaccurate visual representation and complicating color-based analytics.
  • issues/7165, issues/7167, issues/7168
  • Treemap feature enhancement: There is a proposal to add a feature allowing users to fix the size of a parent container while enabling sub-blocks to scale proportionally within that fixed space, improving top-level proportional visualization and internal flexibility without manual sizing.
  • issues/7169
  • Theme switching and styling conflicts: Hard-coded inline styles within SVG elements interfere with seamless dark/light theme switching by causing unreadable graphs when SVGs styled for one theme are combined with CSS for the opposite theme. The issue suggests replacing these inline styles with CSS-based styling to enable graceful and lightweight theme switching.
  • issues/7173
  • Diagram layout and readability problems: Several diagram types suffer from layout and readability issues, including overlapping groups with long text names in architecture diagrams and overflow of longer descriptions in C4 Model diagrams rendered in Firefox.
  • issues/7175, issues/7182
  • Sequence diagram usability improvement: A new syntax is proposed to allow redisplaying participants in the middle of very large sequence diagrams, improving user experience by making participants visible without needing to scroll to the bottom.
  • issues/7179
  • C4 Dynamic Diagram interaction rendering issue: Multiple interactions between the same components are not all rendered in C4 Dynamic Diagrams, as the parser replaces earlier relationships with later ones, causing missing interactions. The request is to display all such relationships without collision.
  • issues/7183
  • SVG logo rendering problem due to CSS rules: SVG logos using rect elements for backgrounds have their fill and opacity unintentionally overridden by a broad CSS rule targeting .image-shape rect, causing rendering problems for icons like AWS logos.
  • issues/7185
  • Architecture diagram connection enhancement: There is a request to add support for diagonal and corner connections in architecture diagrams by introducing syntax to specify corners, enabling the renderer to draw 45-degree diagonal lines between objects.
  • issues/7186
  • Radar chart example syntax error: The radar chart example in the Mermaid.js documentation contains a trailing comma after the last axis definition, causing a parse error and making it difficult to identify and fix the problem due to lack of line number indication.
  • issues/7162, issues/7187

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

Summarized Issues:

As of our latest update, there were no issues closed in the project this week.

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

Key Open Pull Requests

1. fix(pie):longestTextWidth can be -Infinity: This pull request fixes an issue in the pie chart component where the longestTextWidth value could become -Infinity by ensuring it is bounded with a minimum value of 0.

  • URL: pull/7177
  • Merged: No
  • Associated Commits: cd5ce, 5501d, fa9b5

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, addressing the problem described in issue #7159.

  • URL: pull/7172
  • Merged: No
  • Associated Commits: 9df18, 6e869

3. Feature/7078 make changes to allow for decimal values for sequence numbers: This pull request adds support for using decimal values up to the hundredths place for sequence numbers in sequence diagrams, updates the parser and increment logic to handle these decimals accurately, and includes a UI adjustment to reduce font size when sequence numbers become too long.

  • URL: pull/7174
  • Merged: No
  • Associated Commits: 0aca2, 50b21

Other Open Pull Requests

  • Diagram Styling Fixes: Multiple pull requests address styling issues in various diagram types. One fixes the application of user-defined classDef styles in treemap diagrams by resolving type inconsistencies and SVG attribute override issues, ensuring consistency with flowchart and state diagrams. Another fixes font size rendering in Firefox for C4 model descriptions by adding "px" to numeric font sizes, improving visual clarity.
  • pull/7178, pull/7170
  • Git Graph Diagram Enhancements: A pull request introduces a new configuration option showCommitHashLabel that allows users to hide labels for commits with auto-generated hash IDs while still displaying labels for commits with custom IDs. This feature helps keep Git graph diagrams cleaner and more focused on important commits.
  • pull/7184
  • Documentation Updates and Fixes: Documentation improvements include updating the pricing tiers to reflect new information and fixing a parse error by removing a trailing comma from the radar diagram example. These changes enhance the accuracy and usability of the Mermaid documentation.
  • pull/7181, pull/7188

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

Key Closed Pull Requests

1. fix: Fix C4 model diagrams description text fitting: This pull request addresses the issue of description text overflowing in C4 model diagrams by correcting the font size configuration during rendering, specifically fixing the text fitting problem observed in Firefox while ensuring better readability without affecting Chrome and Edge.

  • URL: pull/7166
  • Merged: No
  • Associated Commits: 28510, 1e16e

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
sidharthv96 22 3 0 3
omkarht 13 5 0 0
tractorjuice 16 1 0 0
milesspencer35 8 2 0 0
darshanr0107 5 3 0 0
CNOCTAVE 8 0 0 0
jonathanpoelen 0 0 7 0
No author found 4 0 0 0
Zane0816 3 1 0 0
aristotelos 0 2 2 0

Don't miss what's next. Subscribe to Weekly Project News:
Powered by Buttondown, the easiest way to start and grow your newsletter.