standard / eslint-config-semistandard Goto Github PK

"eslint": "^7.22.0",
"eslint-config-semistandard": "^15.0.1",
"eslint-config-standard": "^16.0.2",
"eslint-plugin-import": "^1.16.0",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-promise": "^4.3.1",
"eslint-plugin-standard": "^5.0.0",
"eslint-webpack-plugin": "^2.5.2",

Node 11.15.0
npm 6.7.0

I want to use semistandard in my eslintrc.js. I tried this:

module.exports = {
  root: true,
  'plugins': [
    'import',
    'node',
    'promise',
    'standard'
  ],
  extends: [
    'semistandard'
  ]
}

I get this:

1:1  error  Definition for rule 'import/first' was not found                     import/first
1:1  error  Definition for rule 'import/no-named-default' was not found          import/no-named-default
1:1  error  Definition for rule 'import/no-webpack-loader-syntax' was not found  import/no-webpack-loader-syntax

What am I misunderstanding here? Are there any better instructions on how to use this config? I thought it was as simple as extending it in the eslint configuration.

Hi,

I tried upgrading one of my projects to ESLint 2.0, but the upgrade failed due to peer dependency conflicts with eslint-config-semistandard

npm ERR! peer dep missing: eslint@^1.0.0, required by [email protected]
npm ERR! peer dep missing: eslint@^1.6.0, required by [email protected]
npm ERR! peer dep missing: eslint-config-standard@^4.0.0, required by [email protected]
npm ERR! peer dep missing: eslint-plugin-promise@^1.0.8, required by [email protected]

Can you please update your dependencies to work with ESLint 2.0+?

Thanks!

What version of this package are you using?
^16.0.0
eslint - V7.21.0

What operating system, Node.js, and npm version?
npm - 6.14.15
node- v12.22.6

What happened?
When adding 'semistandard' to the .eslintrc file in extends, the rules of semistandard are not applied, unless running semistandard directly

What did you expect to happen?
ESLint to adhere to the rules in the semistandard sharable config and throw errors

.eslintrc file:

{
    "root": true,
    "extends": [
      "react-app",
      "semistandard",
      "plugin:jsx-a11y/recommended",
      "prettier"
    ],
    "plugins": [
      "jsx-a11y",
      "react",
      "jest",
      "prettier"
    ],
    "env": {
        "jest": true
      },
    "rules": {
      "comma-dangle": "off",
      "react-hooks/exhaustive-deps": "off"
    }
  }

Any ideas please, as was hoping to use semistandard via the .eslintrc file

It's the same as https://github.com/feross/eslint-config-standard/blob/master/eslintrc.json#L135

Here's what I did

Upgrade to ESLint 9 and import eslint-config-semistandard

import globals from 'globals';
import semistandard from 'eslint-config-semistandard';

export default [
  semistandard,
  {
    ignores: ["dist/**"],
    languageOptions: {
      globals: {
        ...globals.browser,
        ...globals.es2021,
        ...globals.node
      }
    }
  }
];

What I expected to happen

I should be able to import semistandard in eslint.config.js and use it as a default ruleset (see eslint-config-standard usage).

standard/eslint-config-standard@3d1284c

What seems to have happened

ESLint reports the following error:

Oops! Something went wrong! :(

ESLint: 9.0.0

A config object is using the "extends" key, which is not supported in flat config system.

Instead of "extends", you can include config objects that you'd like to extend from directly in the flat config array.

Please see the following page for more information:
https://eslint.org/docs/latest/use/configure/migration-guide#predefined-and-shareable-configs

Any chance of an update that allows eslint 3?

Is there a reason that eslint-config-standard is specified as a peerDependency instead of a direct dependency? If I wanted to create a config which extends this config, it seems I would also need to have eslint-config-standard as a peerDependency as well, which feels odd...

Seems like the 8.0.0 is missing from both the changelog and the tags in the repo, would be neat to have both added 👍

What version of this package are you using? 16.0.0

What operating system, Node.js, and npm version? node 16.14.0 npm 8.3.1

What happened?

What did you expect to happen? just installing it like with eslint version 7.32.0

Are you willing to submit a pull request to fix this bug? I'm not sure how.
This are the packages I'm want to use for my vscode linting:
"eslint": "^8.11.0",
"eslint-config-semistandard": "^16.0.0",
"eslint-plugin-promise": "^6.0.0",

this are the packages that are working great together:
"eslint": "^7.32.0",
"eslint-config-semistandard": "^16.0.0",
"eslint-plugin-promise": "^5.1.0",

let me know if you need any further information

Thanks for this project. It's been very useful for me. :)

I just noticed that the peerDependency upon https://github.com/feross/eslint-config-standard is locked to "^2.0.0", which is preventing me from using this with the latest upstream version of that shared config.

Would you like a PR that allows both v2 and v3 of https://github.com/feross/eslint-config-standard ?

What version of this package are you using?

15.0.0 (latest at time of writing)

What operating system, Node.js, and npm version?

Debian 9 container with Node 10.15 and npm 6.5.

What happened?

Using the latest version of the relevant packages:

    "eslint": "6.5.1",
    "eslint-config-semistandard": "15.0.0",
    "eslint-config-standard": "14.1.0",

But this yields a warning at install time, due to an outdated peerDependencies requirement in this repo:

npm WARN [email protected] requires a peer of eslint-config-standard@^13.0.1 but none is installed. You must install peer dependencies yourself.

This also happens in recent Travis CI builds for this repo (e.g. https://travis-ci.org/standard/eslint-config-semistandard/builds/591805141) since the merging of 5a79865 (#26)

What did you expect to happen?

For latest semistandard and standard to be considered compatible.

Are you willing to submit a pull request to fix this bug?

Yes.

Ref #6.
Ref #4.

Haha, it happened again! :)

https://github.com/feross/eslint-config-standard/releases/tag/v4.0.0-0

NPM v2 complains with an error if I'm trying to forcibly use this newer "standard" package. I've got around this for now with the NPM v3 beta, but it'd be super terrific if you could bump your package.json deps again.

Cheers! <3