Googling for legacy-peer-deps npm reveals that npm 7 now, by default, treats peer dependency issues as errors rather than warnings, hence the problems seen here.
The workaround, for anyone finding this, until the led node is fixed, is to install it manually using --legacy-peer-deps as described above.
See Incompatibility with node-red-dashboard v3 Ā· Issue #86 Ā· Adorkable/node-red-contrib-ui-led Ā· GitHub
However, I fear the node may no longer be supported so it may not receive attention.
So, I forked the repo, and made the dependency change and added it as a local npm dependency ... that worked. Hopefully, the project owner is still maintaining the project!
If you could submit a PR to the author that that makes it easy to implement, and also lets others see the solution so they can install it themselves.
I submitted the PR
1 Like
I think I have the same issue, but not just with the LED.....
I have read this thread twice and am still not sure what I need to do?
Here is my dashboard fail log:
2021-09-30T18:35:40.083Z Install : node-red-dashboard 3.0.4
2021-09-30T18:35:40.086Z npm.cmd install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-dashboard@3.0.4
2021-09-30T18:35:41.617Z [err] (node:6240) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
2021-09-30T18:35:41.617Z [err] (Use `node --trace-warnings ...` to show where the warning was created)
2021-09-30T18:35:41.753Z [err] npm
2021-09-30T18:35:41.753Z [err] ERR! code ERESOLVE
2021-09-30T18:35:41.757Z [err] npm
2021-09-30T18:35:41.757Z [err] ERR! ERESOLVE unable to resolve dependency tree
2021-09-30T18:35:41.757Z [err] npm ERR!
2021-09-30T18:35:41.757Z [err] npm
2021-09-30T18:35:41.757Z [err] ERR! Found: node-red-dashboard@3.0.4
2021-09-30T18:35:41.757Z [err] npm ERR! node_modules/node-red-dashboard
2021-09-30T18:35:41.757Z [err] npm ERR!
2021-09-30T18:35:41.757Z [err] node-red-dashboard@"3.0.4" from the root project
2021-09-30T18:35:41.757Z [err] npm ERR! peer node-red-dashboard@">2.15.0" from node-red-node-ui-iframe@0.2.1
2021-09-30T18:35:41.757Z [err] npm
2021-09-30T18:35:41.757Z [err] ERR! node_modules/node-red-node-ui-iframe
2021-09-30T18:35:41.757Z [err] npm
2021-09-30T18:35:41.757Z [err] ERR! node-red-node-ui-iframe@"~0.2.1" from the root project
2021-09-30T18:35:41.757Z [err] npm ERR!
2021-09-30T18:35:41.757Z [err] 1 more (node-red-node-ui-table)
2021-09-30T18:35:41.757Z [err] npm ERR!
2021-09-30T18:35:41.757Z [err] npm
2021-09-30T18:35:41.757Z [err] ERR! Could not resolve dependency:
2021-09-30T18:35:41.757Z [err] npm ERR!
2021-09-30T18:35:41.757Z [err] peer node-red-dashboard@"^2.23.3" from node-red-contrib-ui-led@0.4.10
2021-09-30T18:35:41.757Z [err] npm ERR! node_modules/node-red-contrib-ui-led
2021-09-30T18:35:41.757Z [err] npm
2021-09-30T18:35:41.757Z [err] ERR! node-red-contrib-ui-led@"~0.4.10" from the root project
2021-09-30T18:35:41.757Z [err] npm ERR!
2021-09-30T18:35:41.757Z [err]
2021-09-30T18:35:41.757Z [err] npm ERR! Fix the upstream dependency conflict, or retry
2021-09-30T18:35:41.757Z [err] npm ERR! this command with --force, or --legacy-peer-deps
2021-09-30T18:35:41.757Z [err] npm ERR!
2021-09-30T18:35:41.757Z [err] to accept an incorrect (and potentially broken) dependency resolution.
2021-09-30T18:35:41.757Z [err] npm
2021-09-30T18:35:41.757Z [err] ERR!
2021-09-30T18:35:41.757Z [err] npm
2021-09-30T18:35:41.757Z [err] ERR! See C:\Users\tbg\AppData\Local\npm-cache\eresolve-report.txt for a full report.
2021-09-30T18:35:41.762Z [err]
2021-09-30T18:35:41.763Z [err] npm ERR! A complete log of this run can be found in:
2021-09-30T18:35:41.763Z [err] npm ERR! C:\Users\tbg\AppData\Local\npm-cache\_logs\2021-09-30T18_35_41_758Z-debug.log
2021-09-30T18:35:41.775Z rc=1
To me, it looks like there is an issue with both ui-iframe and ui-led?
I think this thread is telling me I need to remove them from my project and then the dashboard nodes will update?
Node-red-contrib-ui-led now (V0.4.10) installs on top of Dashboard 3.0.4 without errors or warnings.
You can do that, or add --legacy-peer-deps to the npm command to workaround it. Ideally, you should report this on the offending repo.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
