Topic: npm install in VSCode for standard + vite
*Expected behavior*npm install in VSCode should install all depedencies for Standard + Vite. I get these errors.
*Actual behavior*nickbarling@Mac-Studio mdb5-free-standard-vite % npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: mdb-starter-vite@1.0.0 npm ERR! Found: @babel/core@undefined npm ERR! node_modules/@babel/core npm ERR! dev @babel/core@"^7.19.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer @babel/core@"^7.0.0-0" from @babel/cli@7.21.0 npm ERR! node_modules/@babel/cli npm ERR! dev @babel/cli@"^7.18.10" 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: npm ERR! /Users/nickbarling/.npm/_logs/2023-02-23T05_30_53_773Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in:npm ERR! /Users/nickbarling/.npm/_logs/2023-02-23T05_30_53_773Z-debug-0.lognickbarling@Mac-Studio mdb5-free-standard-vite %
Resources (screenshots, code snippets etc.)
How do I get updated dependencies?
If I understand correctly you used the starter downloaded by MDB CLI? I just checked and npm install didn't return a dependency problem message. What version of node are you using?
You can find a possible solution here: https://stackoverflow.com/questions/64573177/unable-to-resolve-dependency-tree-error-when-installing-npm-packages
Flashart priority commented 1 year ago
Thank you for the link. Do you really think this is a great answer. I understand how to force a dependency conflict. The problem is MDB provides the package and it is clear you guys have not updated the package. babelrc is the issue and I have no idea where to get that update or even if that is not in conflict with other parts of the package should I find it and update successfully? Should I fork out nearly $550 for a Pro MDB license when I can't even get the core dependency packages to work for standard and Vite? I may have to just revert to vanilla bootstrap and run my own SASS. I was hoping for more from MDB.
I may run -force, but why trust the complex site I am building will function especially with all the backend integration I need as well as client and server side validations. Seems too risky.
Probable hack - DO THIS: Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps npm to accept an incorrect (and potentially broken) dependency resolution.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Opened
- ForumUser: Priority
- Premium support: Yes
- Technology: MDB Standard
- MDB Version: MDB5 6.1.0
- Device: Mac Studio M1 Ultra
- Browser: Chrome Version 110.0.5481.100 (Official Build) (arm64)
- OS: macOS Ventura 13.2.1
- Provided sample code: No
- Provided link: No