* next: (27 commits)
chore: Fix type
refactor!: remove MermaidConfig type enum fallback
test: rewrite some `config` vals to tighten types
chore: Add comment for `yy`.
chore: Increase heap size when building
chore: increase `test-util.ts` converage by returning `undefined`
chore: add `vitest` imports to `test-util.ts`
chore: run `pnpm lint:fix`
create `noErrorsOrAlternatives` parser helper function
chore: export `InfoModule` from `infoModule.ts`
docs(parser): create `packages/parser` README.md file
build: build `.langium` file using `generate` from `langium-cli`
build: update `langium` and `langium-cli` to `v2.0.1`
fix: fix if statment logic checks if `parser` is not `undefined`
chore: add a comment illustrate why we build packages sequentially
chore: refactore `&&` into `if` in `populateCommonDb`
chore: remove `./*` part from `exports` in `parser/package.json`
fix: use `execFileSync` instead of `execSync` in `generateLangium`
fix(mermaid): mark `mermaid-parser` dependecy with `^`
reorder `packages/parser` after `packages/mermaid/src/vitepress`
...
Adds a vitepress JsonSchema plugin that automatically loads
the Mermaid Config JSON Schema from a .schema.yaml file and
gets the default values from it.
The `node16` module resolution requires imports to use the `.js` file
extension in type definitions.
`@rollup/plugin-typescript` is needed to make this work with the Vite
setup used by Mermaid.
The module option for Mermaid internally is set to `nodenext`. This is
needed to support `.json` imports. Note that setting `module` to
`node16` or `nodenext` implies a matching `moduleResolution` value.
