Open OldManMeta opened 2 years ago
You can do a --force, but not a great solution!
Same issue for me @OldManMeta so it is not limited to your environment.
I ended up switching over to this and have had no problems: https://github.com/johnwalley/allotment
It's tough putting a project like this out and then attempting to keep up with it all, especially if you have other commitments etc, so this is not a slight on the efforts of this project and I applaud anyone who undertakes the process - I just needed a solution quickly and was unable to contribute to this project with a fix.
@OldManMeta Thanks for pointing out allotment. I used it in one project with good results. In my other projects I can't use it though because leaflet maps dont (seem to) render inside an allotment😢
Just tried to install into a React 18.2.0 solution and got the following:
npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: Orca@1.0.0 npm ERR! Found: react@18.2.0 npm ERR! node_modules/react npm ERR! react@"^18.2.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^16.0.0-0" from react-split-pane@0.1.92 npm ERR! node_modules/react-split-pane npm ERR! react-split-pane@"*" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry
I can't go backwards here in React - any thoughts or advice?