creativetimofficial / ct-vue-argon-dashboard-pro

Vue Argon Dashboard Pro - Premium Bootstrap 5 Vuejs Admin Template
https://www.creative-tim.com/product/vue-argon-dashboard-pro
25 stars 7 forks source link

[Bug] Version 3.0.1 does not install packages #50

Open ezehnder opened 2 years ago

ezehnder commented 2 years ago

Version

3.0.1

Reproduction link

https://www.creative-tim.com/

Operating System

Windows 10

Device

Laptop

Browser & Version

Any

Steps to reproduce

  1. Download a new copy of vue-argon-dashboard-2-pro-v3.0.1.zip
  2. Extract
  3. Open a new terminal, navigate to the folder and run "npm i" command

    What is expected?

    It is expected to download all packages and install them.

    What is actually happening?

    It doesn't, instead it throws the followin error:

npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: vue-argon-dashboard-2-pro@3.0.1 npm ERR! Found: vue@3.2.37 npm ERR! node_modules/vue npm ERR! vue@"3.2.37" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer vue@"^2.6.12" from @fullcalendar/vue@5.11.2 npm ERR! node_modules/@fullcalendar/vue npm ERR! @fullcalendar/vue@"5.11.2" 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.


Solution

It works if I remove these dependencies: "@fullcalendar/core": "5.11.2", "@fullcalendar/daygrid": "5.11.2", "@fullcalendar/interaction": "5.11.2", "@fullcalendar/vue": "5.11.2", "@fullcalendar/vue3": "5.11.2",

but that is not desired, because I want to be able to use fullcalendar as well.

Additional comments

If you cannot reproduce the error, consider trying this on an environment other than your dev environment, start from scratch, because that's what is most likely to happen for most of new customers purchasing and downloading this theme.

Thank you.

sajadevo commented 1 year ago

Hi @ezehnder,

You can ignore this issue when install the dependencies by using the --legacy-peer-deps flag. e.g. npm i --legacy-peer-deps

Regards, Sajad