Weekly GitHub Report for Mermaid: September 29, 2025 - October 06, 2025 (12:04:32)
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.
As of our latest update, there are no active issues with ongoing comments this week.
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.
- 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 or explanation available, causing confusion even for experienced users.
- log scale for
xychart-beta
: This issue proposes adding ascale
string field to thexychart-beta
component that defaults tolinear
but can also acceptlog
as an option, enabling the plotting of logarithmic scales while maintaining version control of the original non-logged data. The enhancement aims to support future extensions to other scale types and includes an example demonstrating how to specify the log scale for chart axes and data series. - 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.
- 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.
- 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 visualize graphs. While the development server runs without errors and displays the graphs correctly, the build process results in a runtime error related to setting properties on an undefined object, causing the application to fail on startup.
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: 18
Summarized Issues:
- Text rendering and markdown issues: Multiple problems occur with text rendering in Mermaid, including incorrect deletion of lines starting with
%%
inside quoted strings, improper Markdown formatting in new shape labels, and removal of Unicode text enclosed in backticks whenhtmlLabels
is false. Additionally, escaped markdown characters and entity codes are inconsistently handled, causing spaces, removal of text, or unintended HTML entities to appear in the output. - [issues/7011, issues/7012, issues/7013, issues/7015, issues/7016]
- Parsing and syntax errors in flowcharts and edges: Mermaid exhibits parsing errors related to syntax inconsistencies such as edge ID and node name conflicts, inconsistent spacing requirements in edge ID definitions, and syntax errors triggered by uppercase letters in IDs or special characters in CSS comments. These issues cause rendering failures or confusing error positioning without clear diagnostics.
- [issues/7022, issues/7024, issues/7031, issues/7032, issues/7033]
- Rendering and export compatibility problems: Exported SVG files from Mermaid charts display correctly in some applications like Chrome but fail to show text in others such as Inkscape or Powerpoint, creating difficulties for users incorporating charts into presentations. Also, specific node names like "click" fail to render in flowcharts despite no errors being reported.
- [issues/7021, issues/7023]
- Feature limitations and customization requests: Users face limitations such as the inability to customize gitGraph commit label positions and broken Fontawesome brand-character syntax, which results in placeholders instead of icons. Additionally, LaTeX equations separated by plain text within node labels fail to render correctly, limiting diagram expressiveness.
- [issues/7027, issues/7029, issues/7034]
- Date and timezone formatting issues: The timezone/UTC offset formatting options
Z
andZZ
in Gantt chart date specifications do not work as documented, preventing proper rendering of tasks with timezone offsets in the mermaidchart.com playground. - [issues/7026]
- Label parsing inconsistencies: Labels in the new shape syntax that begin with a single quote are treated as quoted strings without documentation, causing YAML parsing errors and line number mismatches, suggesting a need to align label string syntax with that used in nodes.
- [issues/7037]
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. Ensure icons render inside mindmap nodes: This pull request ensures that icons are correctly rendered inside mindmap nodes by adding support for icons, improving node label positioning, and organizing the icon logic into a separate file.
- URL: pull/7025
- Merged: No
2. Update free plan diagram limit from 3 to 6: This pull request proposes increasing the diagram limit for the free plan from 3 to 6, aiming to enhance the user experience by allowing more diagrams under the free tier.
- URL: pull/7036
- Merged: No
3. Ensure architecture diagram uses unified rendering: This pull request aims to fix the architecture diagram by ensuring it uses a unified rendering approach for consistency and improved visualization.
- URL: pull/7020
- Merged: No
- Associated Commits: 0a233
Other Open Pull Requests
- Block comments support: This pull request introduces support for block comments in the project, resolving issue #1249 and including both unit and end-to-end tests to ensure functionality. Documentation and changelog updates are still pending for this feature.
- FontAwesome brand icon fix: This pull request corrects the FontAwesome syntax for brand icons by replacing the incorrect "fa" prefix with the correct "fab" prefix, specifically fixing the Twitter icon usage. This ensures that brand icons render properly in the project.
- Gantt chart end date handling fixes: These pull requests improve the Gantt chart module by fixing the end date handling when using complex date formats and excludes, and by updating the endDate calculation logic to correctly account for excluded days like weekends. Additional tests verify that task durations and visual representations accurately reflect real completion dates under these conditions.
- Special character escaping in node labels: This pull request fixes the escaping of special characters (
<
,>
,&
,\
) in node labels when theflowchart.htmlLabels
option is set tofalse
by updating thesanitizeText()
function. This ensures correct rendering of labels without breaking existing behavior forhtmlLabels: true
.
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. mindmap breaking issue in ELK layout: This pull request fixes a mindmap rendering issue in the ELK layout of Mermaid where a type error caused the rendering to fail, ensuring more stable and accurate visualization.
- URL: pull/7019
- Merged: Yes
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 |
---|---|---|---|---|
darshanr0107 | 27 | 7 | 0 | 1 |
shubhamparikh2704 | 26 | 0 | 0 | 6 |
jonathanpoelen | 4 | 3 | 13 | 0 |
omkarht | 14 | 2 | 0 | 1 |
knsv | 10 | 1 | 0 | 0 |
No author found | 10 | 0 | 0 | 0 |
y76 | 6 | 1 | 1 | 1 |
Copilot | 1 | 0 | 0 | 7 |
sidharthv96 | 6 | 0 | 0 | 0 |
SAMARTHAGARWAL77 | 4 | 2 | 0 | 0 |