-
Notifications
You must be signed in to change notification settings - Fork 39
Open
Description
When installing:
$ npm install winston-redis
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/redis
npm ERR! redis@"^3.1.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer redis@"^2.8.0" from [email protected]
npm ERR! node_modules/winston-redis
npm ERR! winston-redis@"*" 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.After removing redis, I saw the winston-redis package.json use older version of redis (2.8.0) :
{
"name": "winston-redis",
"description": "A fixed-length Redis transport for winston",
"version": "3.1.0",
"author": "Charlie Robbins <[email protected]>",
"repository": {
"type": "git",
"url": "[email protected]:winstonjs/winston-redis.git"
},
"keywords": [
"logging",
"sysadmin",
"tools",
"winston",
"redis"
],
"dependencies": {
"async": "^2.6.1",
"lodash": "^4.6.1",
"winston-transport": "^4.2.0"
},
"devDependencies": {
"abstract-winston-transport": "^0.5.1",
"mocha": "^5.2.0",
"redis": "^2.8.0"
},
"peerDependencies": {
"redis": "^2.8.0",
"winston": "^3.0.0"
},
"main": "./lib/winston-redis",
"scripts": {
"test": "mocha test/*-test.js --exit"
},
"engines": {
"node": ">=8.11.x"
},
"license": "MIT"
}
Metadata
Metadata
Assignees
Labels
No labels