Skip to content

[Bug] Version 3.0.1 does not install packages #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ezehnder opened this issue Sep 21, 2022 · 1 comment
Open

[Bug] Version 3.0.1 does not install packages #50

ezehnder opened this issue Sep 21, 2022 · 1 comment

Comments

@ezehnder
Copy link

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
Copy link
Contributor

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

@sajadevo sajadevo reopened this Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants