Skip to content
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

Unable to use zenuml from mermaid #9559

Closed
6 of 7 tasks
davidolrik opened this issue Nov 16, 2023 · 3 comments
Closed
6 of 7 tasks

Unable to use zenuml from mermaid #9559

davidolrik opened this issue Nov 16, 2023 · 3 comments
Labels
closed: duplicate This issue or pull request already exists in another issue or pull request

Comments

@davidolrik
Copy link

Have you read the Contributing Guidelines on issues?

Prerequisites

  • I'm using the latest version of Docusaurus.
  • I have tried the npm run clear or yarn clear command.
  • I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
  • I have tried creating a repro with https://new.docusaurus.io.
  • I have read the console error message carefully (if applicable).

Description

On a brand new installation of Docusaurus I wanted to create a sequence diagram using zenuml, which is part of mermaid since 10.2.3.

In order to add support for zenuml you have to install the support package @mermaid-js/mermaid-zenuml but unfortunately this package has conflicting dependencies with Docusaurus as seen here:

$ npm install --save @mermaid-js/mermaid-zenuml
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: flux@4.0.4
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN   peerOptional react@">= 16.8.0 < 19.0.0" from @docsearch/react@3.5.2
npm WARN   node_modules/@docsearch/react
npm WARN     @docsearch/react@"^3.5.2" from @docusaurus/theme-search-algolia@3.0.0
npm WARN     node_modules/@docusaurus/theme-search-algolia
npm WARN   32 more (@docusaurus/core, @docusaurus/mdx-loader, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^15.0.2 || ^16.0.0 || ^17.0.0" from flux@4.0.4
npm WARN node_modules/@microlink/react-json-view/node_modules/flux
npm WARN   flux@"~4.0.1" from @microlink/react-json-view@1.23.0
npm WARN   node_modules/@microlink/react-json-view
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^15.0.2 || ^16.0.0 || ^17.0.0" from flux@4.0.4
npm WARN   node_modules/@microlink/react-json-view/node_modules/flux
npm WARN     flux@"~4.0.1" from @microlink/react-json-view@1.23.0
npm WARN     node_modules/@microlink/react-json-view

Reproducible demo

No response

Steps to reproduce

  1. npx create-docusaurus@latest docusaurus classic
  2. cd docusaurus
  3. npm install --save @docusaurus/theme-mermaid
  4. npm install --save @mermaid-js/mermaid-zenuml

Expected behavior

@mermaid-js/mermaid-zenuml would install cleanly, so mermaid markdown blocks with zenuml would render.

Actual behavior

Unable to install @mermaid-js/mermaid-zenuml

Your environment

Docusaurus 3.0.0
Node.js v20.9.0
macOS 14.1 (23B74)

Self-service

  • I'd be willing to fix this bug myself.
@davidolrik davidolrik added bug An error in the Docusaurus core causing instability or issues with its execution status: needs triage This issue has not been triaged by maintainers labels Nov 16, 2023
@davidolrik
Copy link
Author

It seems that the culprit is @docusaurus/plugin-debug which dependes on @microlink/react-json-view which has this dependency "flux": "~4.0.1" defined that does not support React 18.

@davidolrik
Copy link
Author

More info here: mac-s-g/react-json-view#403

@Josh-Cena
Copy link
Collaborator

Duplicate of #9486. The error does not mention zenuml, so it surely comes from somewhere else!

@Josh-Cena Josh-Cena closed this as not planned Won't fix, can't repro, duplicate, stale Nov 16, 2023
@Josh-Cena Josh-Cena added closed: duplicate This issue or pull request already exists in another issue or pull request and removed bug An error in the Docusaurus core causing instability or issues with its execution status: needs triage This issue has not been triaged by maintainers labels Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: duplicate This issue or pull request already exists in another issue or pull request
Projects
None yet
Development

No branches or pull requests

2 participants