Skip to main content
Question

Could not resolve dependency: npm ERR! peer axios@"^0.18.1" from box-ui-elements@12.0.0-beta.9 npm ERR! node_modules/box-ui-elements npm ERR!

  • May 22, 2025
  • 4 replies
  • 33 views
C
Forum|alt.badge.img

Getting bunch of errors when trying to npm install box-ui-elements for content uploader.

It seems a lot of dependencies are depreciated.  Is this library and package still working?

https://developer.box.com/guides/embed/ui-elements/uploader/

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: box-ui-elements-demo@0.1.0
npm ERR! Found: axios@0.19.1
npm ERR! node_modules/axios
npm ERR!   dev axios@"^0.19.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer axios@"^0.18.1" from box-ui-elements@12.0.0-beta.9
npm ERR! node_modules/box-ui-elements
npm ERR!   dev box-ui-elements@"^12.0.0-beta.9" 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.

    4 replies

    C
    Forum|alt.badge.img

    Hello, 

    Is this happening with vs 13.0.0 too? It looks like the vs you are installing is a beta?

    Thanks, 

    Alex, Box Developer Advocate

    C
    Forum|alt.badge.img

    wYes it happens with v13 as well.  I've tried --force and --legacy.. nothing seems to resolve the depreciated dependencies. 

     

    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR! 
    npm ERR! While resolving: client@0.1.0
    npm ERR! Found: axios@0.21.4
    npm ERR! node_modules/axios
    npm ERR!   axios@"^0.21.1" from the root project
    npm ERR! 
    npm ERR! Could not resolve dependency:
    npm ERR! peer axios@"^0.18.1" from box-ui-elements@13.0.0
    npm ERR! node_modules/box-ui-elements
    npm ERR!   box-ui-elements@"13.0.0" 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.
    C
    Forum|alt.badge.img

    Let me reach out to that team and report back! Thank you for bringing this up. 

    C
    Forum|alt.badge.img

    Can you confirm what version of npm you are running?  You could consider using the --legacy-peer-deps flag like described here. We verified it works for running npm v6.4.13.

     

    Thanks, 

    Alex

    Terms of ServiceAccessibility statement