eslint-config-standard: dependencies need to be updated (unable to resolve dependency tree)

From what I can read it seems that you want us to upgrade eslint-plugin-promise to 5.x, is that correct?

Yep, it could be cool if we could merge #183 and release a new minor version! 😄

@JustFly1984 Fix by swapping to the correct current peer dependency, unless that causes you some other issue:

yarn add eslint-plugin-promise@^4.2.1

If you use a service such as Dependabot, it consistently tells us to bump eslint-plugin-promise to v5.1.0, it is only after explicitly updating to v5.1.0 that issues are encountered. Doing a clean install of eslint-config-standard will not cause problems, only updating versions of peer dependencies.

Updating to v5.1.0 causes phantom installation errors on a clean install or upgrade, but not npm install if node_modules already exists. It is only causing problems when it is manually installed above the current major in eslint-config-standard in the package.json that it leads to resolution errors.

Yes, it needs proper time to be updated and confirm that everything is still working as intended or if it needs to be scheduled as a major or minor patch, which is what is happening in #183 as far as I can tell. I believe this was to get that ball rolling for sure and make sure everyone is on the same page searching for this error, not for sudden changes overnight. This package is distributed through npm, it cannot be expected that everyone will use legacy options and outdated versions. They may not exist in the future, either. Legacy tends to become a legacy. This issue was made to bring attention to the problem so it can be known and worked on resolving it. The new version resolution is going to change everything going forward and make not keeping up to date all the more problematic for developers.

It is impossible to install eslint-config-standard or upgrade your dependency tree, unless you are using outdated versions or bypassing the new intended installation method.

Looking at the flip side, if someone tried to use a horribly outdated version of node and npm, they would be told to upgrade as it is out of your supported versions. If you are outdated? We get told to use legacy package manager flags or versions. At least that is how I interpreted it.

Indeed, doing npm install -D eslint-plugin-promise will install eslint-plugin-promise@4.3.1 but the current latest version is 5.1.0, might be a bug with npm, I don’t really know, see the package page: https://www.npmjs.com/package/eslint-plugin-promise.

The only thing I can think of that causes you a problem is if you installed a too new eslint-plugin-promise

In my opinion, this package should support most up to date, plugins/package it is actually using, so we should; support the latest version of eslint-plugin-promise with npm@7. @voxpelli

I think this needs a “step to reproduce”. I just tried this with Node 16.0.0 and npm 7.10.0:

1. mkdir test-npm7-standard
2. cd test-npm7-standard
3. npm init
4. npm install -D eslint-config-standard
5. Success ✅

{
  "name": "test-npm7-standard",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "eslint-config-standard": "^16.0.2"
  }
}

If I continue and then do:

1. npm install -D eslint-plugin-promise
2. Success ✅ eslint-plugin-promise@4.3.1 was installed

{
  "name": "test-npm7-standard",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "eslint-config-standard": "^16.0.2",
    "eslint-plugin-promise": "^4.3.1"
  }
}

To get all correct peer dependencies I can use the third party install-peerdeps and do:

1. npx install-peerdeps --dev eslint-config-standard
2. Success ✅

{
  "name": "test-npm7-standard",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "eslint": "^7.24.0",
    "eslint-config-standard": "^16.0.2",
    "eslint-plugin-import": "^2.22.1",
    "eslint-plugin-node": "^11.1.0",
    "eslint-plugin-promise": "^4.3.1"
  }
}

All in all: I’m not sure what is broken? I don’t believe npm 7.10.0 has changed anything relevant to this and Node 16 or 15 doesn’t matter.

The only thing I can think of that causes you a problem is if you installed a too new eslint-plugin-promise prior to upgrading to npm 7 and npm 7 now correctly points out that you are using an unsupported version of eslint-plugin-promise?

Then do a npx install-peerdeps --dev eslint-config-standard and you will be back in sync.