You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting the following error almost 20 times (once for each cordova plugin add command) when running ./build.sh on a completely new clone
> cordova plugin add cordova-plugin-filepath
You have been opted out of telemetry. To change this, run: cordova telemetry on.
Failed to fetch plugin cordova-plugin-filepath@^1.5.8 via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
CordovaError: Error: npm: Command failed with exit code 1 Error output:
npm WARN idealTree Removing dependencies.cordova-plugin-filepath in favor of devDependencies.cordova-plugin-filepath
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @project-sunbird/[email protected]
npm ERR! node_modules/@project-sunbird/client-services
npm ERR! @project-sunbird/client-services@"5.0.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @project-sunbird/client-services@"3.6.x" from @project-sunbird/[email protected]
npm ERR! node_modules/@project-sunbird/common-form-elements-v9
npm ERR! @project-sunbird/common-form-elements-v9@"5.0.3" 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:
I think there are conflicting asks for dependency @sb/client-services ... one directly and one through common-form-elements-v9. Both of them have different major versions
Getting the following error almost 20 times (once for each cordova plugin add command) when running ./build.sh on a completely new clone
There seems to be an issue with [email protected]
The text was updated successfully, but these errors were encountered: