Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

As I am trying to set up a react app thought the apps manager, the build logs inform me about a peer dependency from some of the libraries.
npm ERR! code ERESOLVE
[2022-06-22 21:24:23] npm ERR! ERESOLVE could not resolve
[2022-06-22 21:24:23] npm ERR!
[2022-06-22 21:24:23] npm ERR! While resolving: react-vis@1.11.7
[2022-06-22 21:24:23] npm ERR! Found: react@17.0.2
[2022-06-22 21:24:23] npm ERR! node_modules/react
[2022-06-22 21:24:23] npm ERR! react@"^17.0.2" from the root project
[2022-06-22 21:24:23] npm ERR! peer react@"^16.8 || 17 || 18" from @blueprintjs/core@4.5.0
[2022-06-22 21:24:23] npm ERR! node_modules/@blueprintjs/core
[2022-06-22 21:24:23] npm ERR! @blueprintjs/core@"^4.3.2" from the root project
[2022-06-22 21:24:23] npm ERR! @blueprintjs/core@"^4.5.0" from @blueprintjs/datetime@4.3.0
[2022-06-22 21:24:23] npm ERR! node_modules/@blueprintjs/datetime
[2022-06-22 21:24:23] npm ERR! @blueprintjs/datetime@"^4.3.0" from the root project
[2022-06-22 21:24:23] npm ERR! 2 more (@blueprintjs/popover2, @blueprintjs/select)
[2022-06-22 21:24:23] npm ERR! 21 more (@blueprintjs/datetime, @blueprintjs/popover2, ...)
[2022-06-22 21:24:23] npm ERR!
[2022-06-22 21:24:23] npm ERR! Could not resolve dependency:
[2022-06-22 21:24:23] npm ERR! peer react@"15.3.0 - 16.x" from react-vis@1.11.7
[2022-06-22 21:24:23] npm ERR! node_modules/react-vis
[2022-06-22 21:24:23] npm ERR! react-vis@"^1.11.7" from the root project
[2022-06-22 21:24:23] npm ERR!
[2022-06-22 21:24:23] npm ERR! Conflicting peer dependency: react@16.14.0
[2022-06-22 21:24:23] npm ERR! node_modules/react
[2022-06-22 21:24:23] npm ERR! peer react@"15.3.0 - 16.x" from react-vis@1.11.7
[2022-06-22 21:24:23] npm ERR! node_modules/react-vis
[2022-06-22 21:24:23] npm ERR! react-vis@"^1.11.7" from the root project
[2022-06-22 21:24:23] npm ERR!
[2022-06-22 21:24:23] npm ERR! Fix the upstream dependency conflict, or retry
[2022-06-22 21:24:23] npm ERR! this command with --force, or --legacy-peer-deps
[2022-06-22 21:24:23] npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
I solve this problem locally by using npm i -f, but trying to deploy the app, the systems uses npm ci and I have zero knowledge on how to change that.
Any way to tell the system which command to run when booting the app?
jhonnydepp12
dolphinnn
Vaishnavi Vundyala
016512ea60864da0867e5280f293de
Peter Monadjemi
Prince7hakur
devjk1
fc9acbfbc3124cbf8df28a1c5c5cdb
ab871885551143798f41908c709271
gouskova
Saivion Services