v17 no longer respects env specified in package.json

[GaryGSC]

A minimal reproduction is available at the repo garygsc/standardjs-regression, which has two commits.

What version of this package are you using?
There's a regression when switching from 16.0.4 to 17.0.0 that wasn't documented in the changelog.

What operating system, Node.js, and npm version?
OS: ubuntu-latest (20.04.4)
Node.js version: 16.x (v16.15.0, which comes with npm v8.5.5)

What happened?
Standard exited with exit code 1 and the following errors:

standard: Use JavaScript Standard Style (https://standardjs.com)
  /home/runner/work/standardjs-regression/standardjs-regression/index.test.js:1:1: 'describe' is not defined. (no-undef)
  /home/runner/work/standardjs-regression/standardjs-regression/index.test.js:2:3: 'test' is not defined. (no-undef)
  /home/runner/work/standardjs-regression/standardjs-regression/index.test.js:3:5: 'expect' is not defined. (no-undef)

What did you expect to happen?
Because the package.json specified

"standard": {
  "env": {
    "jest": true
  }
}

we expected exit code 0 with no errors, like what happens with standard@16.0.4.

Are you willing to submit a pull request to fix this bug?
Yeah. It looks like standard-engine's the repo that handles creating an ESLint config from the package.json, so this issue might be in the wrong place.

[klaemo]

Looking at the resolve-eslint-config.js code you linked it seems like the config syntax changed slightly to:

"standard": {
  "env": ["jest"]
}

This also fixed it for me locally.

[LinusU]

@klaemo nice find!

Would be happy to accept a PR to improve the documentation