[
https://issues.apache.org/jira/browse/STREAMPIPES-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466313#comment-17466313
]
Philipp Zehnder commented on STREAMPIPES-491:
---------------------------------------------
Hi,
can you try to run "npm install --legacy-peer-deps".
I am not sure why this is the case and we should update the dependencies in the
UI.
Currently we are working on increasing the e2e test coverage which should also
help us to change dependencies more easily and to find bugs directly.
> Incompatible dependencies within the ui
> ---------------------------------------
>
> Key: STREAMPIPES-491
> URL: https://issues.apache.org/jira/browse/STREAMPIPES-491
> Project: StreamPipes
> Issue Type: Bug
> Components: UI
> Reporter: Ben Hutcheson
> Priority: Minor
>
> Just starting building a test environment focused on the ui component and ran
> into an issue with running npm install.
> It seems there are a few dependency conflicts due to certain versions being
> pinned.
>
> {code:java}
> npm ERR! code ERESOLVE
> npm ERR! ERESOLVE unable to resolve dependency tree
> npm ERR!
> npm ERR! While resolving: [email protected]
> npm ERR! Found: [email protected]
> npm ERR! node_modules/codemirror
> npm ERR! codemirror@"5.55.0" from the root project
> npm ERR!
> npm ERR! Could not resolve dependency:
> npm ERR! peer codemirror@">=5.63.3" from @ctrl/[email protected]
> npm ERR! node_modules/@ctrl/ngx-codemirror
> npm ERR! @ctrl/ngx-codemirror@"5.1.1" 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! See /home/missy/.npm/eresolve-report.txt for a full report.npm ERR!
> A complete log of this run can be found in:
> npm ERR! /home/missy/.npm/_logs/2021-12-29T00_03_45_604Z-debug.log
> {code}
> I am using npm version 7.5.2 and was thinking about rolling back to v6 but
> wanted to check to see if I am doing something wrong.
> I also started to manually go through and update dependencies but wasn't sure
> if there was a reason to hold certain packages back?
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
