Weekly Project News

Subscribe
Archives

Weekly GitHub Report for Mermaid: August 11, 2025 - August 18, 2025 (12:03:56)

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. External SVG sprite rendering fails: This issue describes a problem where Mermaid fails to render SVG icons correctly when using an external SVG sprite, although individual external SVG files render without issues. The user highlights the importance of supporting external SVG sprites to reduce network calls and improve rendering performance for diagrams with many icons, noting that native icon resolution on GitHub is also problematic.

    • The maintainers confirmed that the current Mermaid implementation does not support external SVG sprites and recommended using direct SVG files instead. The user responded by emphasizing the performance drawbacks of multiple network calls and the necessity of external sprite support for complex diagrams, also referencing a related issue about native icon sets.
    • 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 addresses the lack of explanatory tooltips for emoji used next to diagram type names in the "Diagram Syntax" section of the documentation, which currently leaves users unclear about the meaning of these icons. The proposal suggests adding tooltips to these emoji to improve user understanding and provide clear information about what each icon represents.
  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 the plotting of logarithmic scales. This enhancement aims to allow users to version control graph descriptions with true (non-logged) values while displaying the data on a log scale, with potential for future extension to other scale types.
  3. 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 height adjustments and text clipping in the SVG output. Specifically, 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 a corresponding height change, affecting the visual accuracy of the rendered diagrams.
  4. 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. Since there were fewer than 5 open issues, all of the open issues have been listed above.

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:

  • SVG Icon Rendering Issues: Mermaid fails to render SVG icons properly when using an external SVG sprite containing multiple icons, although individual external SVG files render correctly. Additionally, Mermaid's native icon sets do not render correctly on GitHub, despite working in Visual Studio Code, causing inconsistencies across platforms.
  • issues/6844, issues/6848
  • Sequence Diagram Parsing Errors: Adding a participant with a long alias containing HTML tags in a Mermaid sequenceDiagram causes the editor to hang and throw an "InternalError: too much recursion" error. This issue is linked to the parser failing to recognize the "AS" token and shows different behaviors in Firefox and Chrome browsers.
  • issues/6853
  • Markdown Support Requests: There is a request to add markdown support for various elements such as codeblocks, monospaced text, links, lists, quotes, headings, and images to enhance Mermaid's documentation and diagram capabilities.
  • issues/6858
  • CSS Variable Support in Themes: Users request support for CSS variables within the themeVariables configuration to allow styling of Mermaid graphs that better align with their design language.
  • issues/6860

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

Summarized Issues:

  • Flow and Layout Configuration: The issues discuss aspects of flow diagrams and layout customization in Mermaid. One issue is about the general topic of flow, while another focuses on exposing specific ELK layout options to users for better control over node and edge ordering without increasing edge crossings.
  • [issues/6840, issues/6856]

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

Key Open Pull Requests

1. Update elk layout to handle start/stop of edges properly for all shapes: This pull request updates the ELK layout algorithm in the Mermaid project to properly handle the start and stop points of edges for all shapes, improving intersection calculations and rendering flow, and separates ELK-related changes from the mindmap features for better modularity and maintainability.

  • URL: pull/6854
  • Merged: No
  • Associated Commits: 1e641, c8e50, 4c8c4, 1e3ea, f2eef, 34027, fbae6, e7208, eadb3, d2463, c13ce, ba52e, f0445, 4c3de, c7f2f, b7c03, 83145, c95c6, e2ce0, 6fcdf, f0bca, 2f186, d7308, 074f1, b6178, b51b9, a4aa2, f48e6, 01ce8, b296d, 6a6a3, 204a9, e6842, 688d9, 28717, 68c01, 15074, dd360, 81b0f, 11abf, a716a

2. 6623: add image and icon support for sequence diagrams: This pull request extends Mermaid sequence diagrams by adding support for custom images and Font Awesome icons to visually represent participant actors using a JSON-based syntax, thereby enhancing diagram readability and bringing sequence diagrams to visual parity with flowchart capabilities.

  • URL: pull/6852
  • Merged: No
  • Associated Commits: b8673, 71e4d, b8b12, 97481, 0386e, 41e3d, 6b64b

3. Fixed edge animation for hand drawn shapes: This pull request fixes the issue where the edge-animation-* class was not applied to edges in the hand drawn style by refactoring the code to ensure the animation class is correctly added, improving the edge animation for hand drawn shapes.

  • URL: pull/6843
  • Merged: No
  • Associated Commits: 18703, 32723, e6fb4

Other Open Pull Requests

  • Diagram styling enhancements: This pull request adds a new $lineStyle parameter to the UpdateRelStyle command in C4 diagrams, allowing users to choose between solid, dashed, or dotted line styles for relationships. It includes SVG stroke-dasharray rendering, comprehensive unit and visual tests, updated documentation, and demo examples, all while maintaining backward compatibility.
  • pull/6845
  • Dependency upgrades and maintenance: This pull request upgrades the dependencies unocss from version 66.0.0 to 66.4.2 and @iconify/utils from 2.3.0 to 3.0.1, focusing on dropping CommonJS support in @iconify/utils without affecting Mermaid, which is ESM-only. It ensures compliance with contribution guidelines and includes necessary tests and documentation.
  • pull/6846

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. fix: fallback to raw text instead of rendering Unsupported markdown: This pull request fixes the issue of data loss by changing the behavior to fallback to displaying raw text instead of rendering "Unsupported markdown" or empty boxes when unsupported markdown is encountered, ensuring that the original content is preserved when htmlLabels is true or false.

  • URL: pull/6855
  • Merged: Yes
  • Associated Commits: d7401, da90f, 7af67, d1ae6, 60fee, 9c071, 52be2, accb4, 6a628

2. Feat: Add editor selection A/B test: This pull request introduces an A/B test for the Editor selection modal in the Mermaid project, including UI updates and design refinements to evaluate different user interface variants.

  • URL: pull/6847
  • Merged: Yes
  • Associated Commits: 2a514, 18642, 9e81e, 62dee

3. Make elk not force node model order, but strongly consider it instead: This pull request modifies the ELK layout integration in Mermaid to stop forcing a strict node model order and instead strongly consider it, improving node ordering in models with crossings by allowing ELK to optimize layout while still preventing regressions related to node order, and includes an added end-to-end test and changeset.

  • URL: pull/6849
  • Merged: Yes
  • Associated Commits: 4f244, 22609

Other Closed Pull Requests

  • Configuration schema updates: This topic includes pull requests that enhance the Mermaid configuration schema by adding new options and updating related documentation, tests, and changelogs. These changes improve the flexibility and clarity of configuration settings for users.
  • pull/6857
  • Documentation improvements: This topic covers pull requests focused on refining documentation to improve clarity and prevent confusion, such as renaming terms in integration lists. These updates help users better understand the project and its components.
  • pull/6861

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 37 3 0 0
sidharthv96 16 1 0 17
shubhamparikh2704 23 1 2 6
omkarht 23 2 2 0
knsv 12 2 1 0
Copilot 0 0 0 10
saurabhg772244 5 1 0 3
Prashant-7718 8 0 0 0
MrCoder 7 0 0 0
SaanchitaV 0 0 5 2

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