search

creativetimofficial / ct-nuxt-argon-dashboard-pro-laravel-bs4

Nuxt SPA Argon template connected to working Laravel REST API with the help of json:api standard
3 stars 0 forks source link

vue and vue-server-renderer versions incompatible #4

Closed justincervantes closed 2 years ago

justincervantes commented 3 years ago

Prerequisites

Please answer the following questions for yourself before submitting an issue.

Expected Behavior

npm versions should be the same for vue and vue-server-renderer

Current Behavior

npm run build refuses to complete, throwing the below error. I can only resolve it by manually changing my vue versionto 2.6.14 from 2.6.12.

✖ Nuxt Fatal Error
│ Error:
│
│ Vue packages version mismatch:
│
│ - vue@2.6.12
│ - vue-server-renderer@2.6.14

Failure Information (for bugs)

Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.

Steps to Reproduce

  1. Download package
  2. cd into file
  3. npm i
  4. npm run dev

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

nuxt-argon-dashboard-pro@1.3.0 dev C:\Users\Justin Cervantes\Downloads\nuxt-argon-dashboard-pro-v1.3.0 nuxt

ENV development 09:38:56

FATAL 09:38:56

Vue packages version mismatch:

This may cause things to work incorrectly. Make sure to use the same version for both.

Vue packages version mismatch:

✖ Nuxt Fatal Error
│ Error:
│
│ Vue packages version mismatch:
│
│ - vue@2.6.12
│ - vue-server-renderer@2.6.14

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! nuxt-argon-dashboard-pro@1.3.0 dev: nuxt npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the nuxt-argon-dashboard-pro@1.3.0 dev script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:...\npm-cache_logs\2021-09-10T15_38_56_800Z-debug.log

teamupdivision commented 3 years ago

Hi @justincervantes,

Thanks for reporting this issue and for using Creative Tim products.

We did more types of tests, but unfortunately, we were not able to reproduce the error. However, the solving steps should be:

rm package-lock.json rm -rf node_modules npm update npm install

If this doesn’t work, could you try to install with another npm version? This may be another way to solve this.

Please let us know.

Best, UPDIVISION Team

teamupdivision commented 3 years ago

Hi @justincervantes,

We would like to check if the issue was solved. Please let us know if there is anything else we can help with and if you have any other issues.

Best, UPDIVISION Team

teamupdivision commented 2 years ago

Hi @justincervantes,

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).