Here are some breaking changes that I want to get into mermaid-cli v11, once v11 of mermaid comes out:
BREAKING CHANGES
chore!: bump required Node.JS version to 18.19
Node.JS v18.19 is the version of Node.JS that is available in Debian 12 and Ubuntu 24.04, so it's a good minumum version for us to support to.
Resolves #618
chore(dev-deps)!: bump FontAwesome to v6
build!: make puppeteer a peerDependency
Make puppeteer a peerDependency so that users can pick which versions of Puppeteer they want to install.
I've specified that the allowable versions are: ^19 || ^20 || ^21 || ^22. I've also upgraded our tests to run with Puppeteer v22.
Most package managers will automatically pick a version of puppeteer for users to install, but users will be able to override this.
Resolves #627
chore!: remove deprecated parseMMD function
Non-breaking changes
build: use npm instead of yarn
Yarn v1 is quite outdated and newer versions of npm have similar
features now. Basically, instead of having to run yarn xxxxx, we can now just run npm xxxxx instead.
Resolves #529
:straight_ruler: Design Decisions
Some other changes in this PR are part of:
699
700
So we should rebase this branch on master once those PRs are merged.
:bookmark_tabs: Summary
Here are some breaking changes that I want to get into
mermaid-cliv11, once v11 of mermaid comes out:BREAKING CHANGES
build!: make puppeteer a peerDependency
puppeteerapeerDependencyso that users can pick which versions of Puppeteer they want to install.I've specified that the allowable versions are:
^19 || ^20 || ^21 || ^22. I've also upgraded our tests to run with Puppeteer v22.Most package managers will automatically pick a version of
puppeteerfor users to install, but users will be able to override this.Non-breaking changes
yarn xxxxx, we can now just runnpm xxxxxinstead.:straight_ruler: Design Decisions
Some other changes in this PR are part of:
699
700
So we should rebase this branch on
masteronce those PRs are merged.:clipboard: Tasks
Make sure you
masterbranch