Closed ghost closed 3 years ago
Hi @japrehm,
Thanks for reporting the issue and for using Creative Tim products.
Could you try updating the node version to 15.0.0 or more?
Please let us know if this worked.
All the best, UPDIVISION Team
@teamupdivision
I am using node v15.10.0 and npm 7.17.0.
Hi @japrehm,
Thanks for the quick response and confirmation. It looks like there was confusion or a misunderstanding somewhere. It should work with less than 15.0.0. Sorry for the confusion.
Please let us know if this is working well or if there are any other issues.
Best, UPDIVISION Team
Ok, I downgraded to Node v14.17.1 and npm to 6.14.13.
npm install
now works now. Are there any plans to upgrade this to be compatible with newer versions of node/npm?
But when I do npm run serve
I am getting this message
WARNING Compiled with 1 warnings
warning in ./src/store/modules/auth.js
"export 'VueAuthenticate' was not found in 'vue-authenticate'
I can fix the error by updating the auth.js
file line 3 to import VueAuthenticate from "vue-authenticate";
But then the login button on the home screen does not work.
Hi @japrehm,
Thank you very much for the additional details. We're investigating this issue and we'll get back shortly.
Also, we're considering this upgrade, thanks.
Best, UPDIVISION Team
Hi @japrehm,
We've pushed a fix to this problem. You can access it by downloading the product from the downloads section in the Creative Tim website.
Please make sure you install project dependencies (npm install) after downloading the updates.
Let us know if all works well now and there is anything else we can help with.
All the best, UPDIVISION Team
I'm having a similar issue, but when I go to the downloads page it still downloads the same zip files... I purchased the laravel bundle and not the individual template, so I'm hoping that is the snafoo there... any chance the bundle links can also be updated?
Hi @cjholowatyj,
Thanks for your message and for reporting this issue. Can you please share with us the json file you downloaded here? It will help a lot in investigating this further.
Thank you, UPDIVISION Team
I'm still seeing that it is version 1.0.0 as well, but it looks like this might just be an issue with the website versioning? The only change in the package.json file is the vue-authenticate verison? From "vue-authenticate": "^1.4.1",
to "vue-authenticate": "1.4.1"
.
I was able to get vue-authenticate working with the old version by changing the auth.js file line 9 from const vueAuth = new VueAuthenticate(Vue.prototype.$http, {
to const vueAuth = VueAuthenticate.factory(Vue.prototype.$http, {
which will allow us to keep the package updated.
So the package.json version I'm using is showing v1.1.0 which I can see was updated June 29th, 2021 (though again, in the bundle I purchased it displays on the webpage as 1.0.0) I have zipped and attached as requested. package.json.zip
I'm currently getting the following error output when attempting to run npm update
to refresh the dependencies (lockfile warnings excluded):
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: vue-argon-dashboard-pro@1.1.0
npm ERR! Found: eslint@7.30.0
npm ERR! node_modules/eslint
npm ERR! eslint@"^7.1.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^5.0.0 || ^6.0.0" from eslint-plugin-vue@6.2.2
npm ERR! node_modules/eslint-plugin-vue
npm ERR! eslint-plugin-vue@"^6.2.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.
npm ERR!
npm ERR! See /Users/cjholowatyj/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/cjholowatyj/.npm/_logs/2021-07-05T05_40_54_948Z-debug.log
If I run npm update --legacy-peer-deps
it completes successfully (though warns of 24 vulnerabilities) but I still cannot see the dashboard on the front-end
Hi @cjholowatyj,
Thanks for checking. Just to be sure, what is the node version you are using. Is it less than 15.0.0.? Please let us know.
@japrehm Just checking if the issue was solved or if there is anything else we can do.
Please let us know.
Best, Updivision Team
My bad @teamupdivision I was using node v16.4.0. It has to be under v15, right?
Hi @cjholowatyj,
Thanks for the confirmation. Yes, this is correct. In case there is anything else we can help with, please let us know.
Best, Updivision Team
Hi there @japrehm @cjholowatyj,
We would like to check if the issues were solved and if there is anything else we can help with. Please let us know if you have any other issues.
All the best, Updivision Team
Hi @cjholowatyj @japrehm,
Hope this solved the problem. We will go ahead and close this ticket. If there is anything else that can be fixed or we can help with, please let us know.
Best, UPDIVISION Team
P.S. If you need help with any of your projects, we're happy to get in touch. We do custom development for start-ups and companies across the globe (you can check out our portfolio here https://updivision.com/portfolio and some happy clients over here https://updivision.com/testimonials). Don`t hesitate to drop us a line at office@updivision.com or by using our contact form (https://updivision.com/contact).
Hi guys,
You can use nvm for different versions of node, like this:
nvm list
nvm use xxx
And, Another point to keep my mind is that:
rm -r node_modules
rm package-lock.json
npm cache clean --force
npm install --save --legacy-peer-deps
npm audit fix --force
SKIP_PREFLIGHT_CHECK=true
Now, start your project.
Yours faithfully, Parham
亲测有效,cnpm install 就好了!
Prerequisites
Expected Behavior
When setting up the application,
npm install
fails.cd your-vue-argon-dashbord-project
npm install
Current Behavior
Could not resolve dependency: peer eslint@"^5.0.0 || ^6.0.0" from eslint-plugin-vue@6.2.2 node_modules/eslint-plugin-vue eslint-plugin-vue@"^6.2.2" from the root project
Failure Information (for bugs)
Steps to Reproduce
cd your-vue-argon-dashbord-project
npm install
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
Failure Logs