search

creativetimofficial / ct-nextjs-material-dashboard-pro-material-ui-v4

NextJS version of Material Dashboard PRO
https://demos.creative-tim.com/nextjs-material-dashboard-pro-material-ui-v4/admin/dashboard
1 stars 0 forks source link

[Bug] npm install fails #2

Open madhuvanesh opened 8 months ago

madhuvanesh commented 8 months ago

Version

nextjs-material-dashboard-pro-v1.1.0

Reproduction link

https://jsfiddle.net/

Operating System

Windows 11 Home

Device

System SKU LENOVO_MT_82FG_BU_idea_FM_IdeaPad 5 15ITL05 Processor 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz, 2803 Mhz, 4 Core(s), 8 Logical Processor(s)

Browser & Version

Version 121.0.6167.189 (Official Build) (64-bit)

Steps to reproduce

  1. Download NextJS Material Dashboard PRO Material-UI v4 from https://www.creative-tim.com/downloads
  2. Unzip the ZIP file that was downloaded in step (1): nextjs-material-dashboard-pro-v1.1.0.zip
  3. Open the unzipped folder in VSCode
  4. Open the Terminal in VSCode and then: npm install
  5. I see these errors: ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: nextjs-material-dashboard-pro@1.1.0 npm ERR! Found: react@17.0.1 npm ERR! node_modules/react npm ERR! react@"17.0.1" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^16.6.1" from react-big-calendar@0.30.0 npm ERR! node_modules/react-big-calendar npm ERR! react-big-calendar@"0.30.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. npm ERR! npm ERR! npm ERR! For a full report see: npm ERR! C:\Users\madhu\AppData\Local\npm-cache_logs\2024-02-27T20_18_50_671Z-eresolve-report.txt

I get errors on running with --force or --legacy-peer-deps as well. When I copied those errors here I could not submit this issue in my previous try.

What is expected?

npm install should run successfully so I can then run npm run dev

What is actually happening?

The product is not working and I need a refund!!!:(

Solution

  1. Please refund since I have lost faith in the product given how long I have struggled to fix the issues:(

Additional comments

  1. You need to test your product before release.
trungprivate commented 6 months ago

I am having the same issue, is there a solution for this other than using npm install --force?