docify npm error - @mermaid-js/layout-elk

[chandralanka]

Bug Report

npm install have the below error after running docify and npm install commands
PS \docs\output> npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @docusaurus/theme-mermaid@3.10.0
npm ERR! Found: @mermaid-js/layout-elk@0.2.1
npm ERR! node_modules/@mermaid-js/layout-elk
npm ERR! @mermaid-js/layout-elk@"^0.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @mermaid-js/layout-elk@"^0.1.9" from @docusaurus/theme-mermaid@3.10.0
npm ERR! node_modules/@docusaurus/theme-mermaid
npm ERR! @docusaurus/theme-mermaid@"^3.9.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @mermaid-js/layout-elk@0.1.9
npm ERR! node_modules/@mermaid-js/layout-elk
npm ERR! peerOptional @mermaid-js/layout-elk@"^0.1.9" from @docusaurus/theme-mermaid@3.10.0
npm ERR! node_modules/@docusaurus/theme-mermaid
npm ERR! @docusaurus/theme-mermaid@"^3.9.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! \AppData\Local\npm-cache_logs\2026-04-26T19_28_19_190Z-eresolve-report.txt

Steps to Reproduce:

• Calm cli version
  calm --version
  1.37.0

Docusaurus version: 3.10.0
Node version: v22.19.0

• Run calm docify on the parent directory
  CD into calm project directory and run :
  calm docify -a ./architectures/ecommerce-platform.json -o docs/output -u url-mapping.json

• Run npm install
  CD into /docs/output
  run: npm install

Expected Result:

npm install should run with out errors
npm start should display the webpage http://localhost:3000 with calm documentation

package.json

{
"name": "arch-docs",
"version": "1.0.0",
"private": true,
"scripts": {
"start": "docusaurus start",
"build": "docusaurus build",
"serve": "docusaurus serve",
"clear": "rm -rf node_modules/.cache build"
},
"dependencies": {
"@docusaurus/core": "^3.9.0",
"@docusaurus/preset-classic": "^3.9.0",
"@docusaurus/plugin-content-docs": "^3.9.0",
"@docusaurus/theme-classic": "^3.9.0",
"@docusaurus/theme-live-codeblock": "^3.9.0",
"@docusaurus/theme-mermaid": "^3.9.0",
"@mermaid-js/layout-elk": "^0.2.0",
"docusaurus-plugin-search-local": "^2.1.2",
"react": "^18.0.0",
"react-dom": "^18.0.0",
"unist-util-visit": "^5.0.0"
}
}

if you change this "@mermaid-js/layout-elk": "^0.2.0", to "@mermaid-js/layout-elk": "^0.1.9", npm install works.
However, npm start has errors

[jimthompson5802]

@chandralanka this looks like a duplicate of #2323 which was closed by PR #2324.

In meantime, until a new calm cli is released with the fix, there is a manual work-around. After running the calm docify and before the npm install, modify the package.json that is created in the output directory created by the calm docify command to contain the npm overrides field. Once this modification is made the npm install should work.

  "overrides": {
    "@mermaid-js/layout-elk": "^0.2.0",
    "webpackbar": "^7.0.0"
  }

The modified package.json should look like this...

  "name": "arch-docs",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "start": "docusaurus start",
    "build": "docusaurus build",
    "serve": "docusaurus serve",
    "clear": "rm -rf node_modules/.cache build"
  },
  "dependencies": {
    "@docusaurus/core": "^3.9.0",
    "@docusaurus/preset-classic": "^3.9.0",
    "@docusaurus/plugin-content-docs": "^3.9.0",
    "@docusaurus/theme-classic": "^3.9.0",
    "@docusaurus/theme-live-codeblock": "^3.9.0",
    "@docusaurus/theme-mermaid": "^3.9.0",
    "@mermaid-js/layout-elk": "^0.2.0",
    "docusaurus-plugin-search-local": "^2.1.2",
    "react": "^18.0.0",
    "react-dom": "^18.0.0",
    "unist-util-visit": "^5.0.0"
  },
  "overrides": {
    "@mermaid-js/layout-elk": "^0.2.0",
    "webpackbar": "^7.0.0"
  }
}

[rocketstack-matt]

This was already fixed but there was an issue with the CLI release job - that has been fixed, please test with 1.38.0