-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release a mermaid-lite
version?
#4616
Comments
This would be pretty easy to do, if we split up Mermaid into multiple packages (see #4120), e.g. something like:
That way, users can easily build their own version of mermaid, and we could easily create a See further discussion in #4120 (comment) |
I'm more of a fan of splitting diagrams into separate packages. How and why we should select specific diagrams to be in that |
We should figure out a way to mostly-automate releases (except entering the TOTP), otherwise, releasing many packages will be a burden. |
Would not releasing mermaid-lite become an additional routine too? |
Is there a particular problem with automated releases? |
It gets a bit complicated with a mono-repo. How do you handle making Something like https://github.com/changesets/changesets or https://github.com/semantic-release/semantic-release might be nice to automate this. Mermaid's current release notes process is pretty bad (see #4637, #3775, and #3022), and that's with only a single |
@knsv can switch to changesets? I've seen that being used by many monorepo based projects quite well. |
maybe related to #2459? |
This will include all the popular diagrams that use the default layout engine.
This will help solve issues like https://github.com/orgs/mermaid-js/discussions/4314#discussioncomment-6348707
This will not have lazy loading, and will only support the basic diagrams.
The text was updated successfully, but these errors were encountered: