Closed
Description
Discussed in #4680
Originally posted by theSmartRed April 3, 2023
I am trying to run the private chat example following the readme instructions but I see this error trying to install the client side
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @vue/cli-service@undefined
npm ERR! node_modules/@vue/cli-service
npm ERR! dev @vue/cli-service@"~4.5.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @vue/cli-service@"^3.0.0 || ^4.0.0-0" from @vue/[email protected]
npm ERR! node_modules/@vue/cli-plugin-babel
npm ERR! dev @vue/cli-plugin-babel@"~4.5.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.
I am using Node 18.15 and NPM 9.5 that are the current LTS versions for both. How to fix?
On the server side trying to run I see:
Node.js v18.15.0
Worker 1737 died
node:events:491
throw er; // Unhandled 'error' event
^
Error: connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
Emitted 'error' event on RedisAdapter instance at:
at Redis.onError (/Users/lelio.faieta/Documents/Sites/private-messaging/server/node_modules/socket.io-redis/dist/index.js:65:22)
at Redis.emit (node:events:513:28)
at Redis.silentEmit (/Users/lelio.faieta/Documents/Sites/private-messaging/server/node_modules/ioredis/built/redis/index.js:553:26)
at Socket.<anonymous> (/Users/lelio.faieta/Documents/Sites/private-messaging/server/node_modules/ioredis/built/redis/event_handler.js:191:14)
at Object.onceWrapper (node:events:628:26)
at Socket.emit (node:events:525:35)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -61,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 6379
}
this is just an example since it keeps looping on this kind of error