Babylon.js Editor install dependency errors

Questions
1

I am cloning Babylon.js Editor from GitHub - BabylonJS/Editor: Community managed visual editor for Babylon.js
Running npm install
And getting the following errors:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: flexlayout-react@0.6.6
npm ERR! Found: react@16.12.0
npm ERR! node_modules/react
npm ERR! react@“16.12.0” from the root project
npm ERR! peer react@“>=16.0.0” from @ant-design/icons@4.7.0
npm ERR! node_modules/@ant-design/icons
npm ERR! @ant-design/icons@“^4.7.0” from antd@4.18.7
npm ERR! node_modules/antd
npm ERR! antd@“4.18.7” from the root project
npm ERR! 47 more (@ant-design/react-slick, @blueprintjs/core, …)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@“^17.0.2” from flexlayout-react@0.6.6
npm ERR! node_modules/flexlayout-react
npm ERR! flexlayout-react@“0.6.6” from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR! peer react@“^17.0.2” from flexlayout-react@0.6.6
npm ERR! node_modules/flexlayout-react
npm ERR! flexlayout-react@“0.6.6” 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.

I tried doing it on Windows10 and on OSX and am getting the same output.

Here are some things I’ve tried on Windows 10 to fix it:

  • Updating dependencies with:
    npm install --legacy-peer-deps

  • Upgrading react with:
    npm install react@17 react-dom@17

  • Force install:
    npm install --force

  • installing the latest versions of electron-rebuild and node-gyp with:
    npm install -g electron-rebuild
    npm install -g node-gyp

  • Installing visual studio tools:
    npm install --global windows-build-tools

That actually ended up causing more errors, so I found that those tools have been deprecated now and uninstalled them.
I then reinstalled node.js and installed all the tools with it.

  • Manually modifying visual studio to include all the C++ and nodeJS related packages.

Please let me know if you have ideas of what’s going wrong and what else I could try.
Thank you!

2

This was report in [Fix peer dependencies to avoid --legacy-peer-deps · Issue #413 · BabylonJS/Editor · GitHub](https://Bug #413) but doesn’t seem to have ever been fixed.

As you report, running npm i --legacy-peer-deps now fails hard. I’ve updated the bug linked above.

@julien-moreau ?