evgenyorekhov / eslint-config-hardcore Goto Github PK

https://github.com/mysticatea/eslint-plugin-eslint-comments

https://github.com/sindresorhus/eslint-plugin-unicorn/blob/master/docs/rules/prevent-abbreviations.md

It needs to be battle-tested first.

• Check for open issues for the rule before starting working on this issue: https://github.com/sindresorhus/eslint-plugin-unicorn/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+abbreviations

• https://github.com/eslint/eslint/blob/master/conf/eslint-recommended.js
• https://github.com/xjamundx/eslint-plugin-promise/blob/master/index.js

Do not declare the node env:

• in README.md
• in release notes

https://github.com/kellyselden/eslint-plugin-json-files

Waiting for:

• kellyselden/eslint-plugin-json-files#40 (blocker)
• kellyselden/eslint-plugin-json-files#35
• kellyselden/eslint-plugin-json-files#36
• kellyselden/eslint-plugin-json-files#37
• kellyselden/eslint-plugin-json-files#38
• kellyselden/eslint-plugin-json-files#39

https://github.com/SonarSource/eslint-plugin-sonarjs

A Shareable Config should not disable rules.

https://github.com/sindresorhus/eslint-plugin-unicorn/blob/master/docs/rules/prefer-spread.md

https://github.com/freaktechnik/eslint-plugin-array-func#prefer-array-from

https://stackoverflow.com/questions/40548213/array-from-vs-spread-syntax

JSLint's rule for the ternary operator is different now.

Should change the "indent" rule to

        "indent": [
            "error",
            4,
            { 
                "ignoredNodes": [
                    "ConditionalExpression"
                ]
            }
        ],

https://github.com/dustinspecker/eslint-plugin-no-use-extend-native

Compare:

h(
    Component,
    {
        someProp: 123,
        anotherProp: 321
    },
    [
        h(Component, {
            someProp: 123,
            anotherProp: 321
        }),
        h(Component, {
            someProp: 123,
            anotherProp: 321
        }),
        h(
            Component,
            {
                someProp: 123,
                anotherProp: 321
            },
            [
                h(Component, {
                    someProp: 123,
                    anotherProp: 321
                }),
                h(Component, {
                    someProp: 123,
                    anotherProp: 321
                })
            ]
        )
    ]
);

h(Component, {someProp: 123, anotherProp: 321}, [
    h(Component, {someProp: 123, anotherProp: 321}),
    h(Component, {someProp: 123, anotherProp: 321}),
    h(Component, {someProp: 123, anotherProp: 321}, [
        h(Component, {someProp: 123, anotherProp: 321}),
        h(Component, {someProp: 123, anotherProp: 321})
    ])
]);

Perhaps the "object-property-newline" rule should be reconfigured to

["error", {"allowAllPropertiesOnSameLine": true}]

1. Create .eslintrc.json file with the following contents: {"extends": ["./index.json"]}.
2. Change the test script to node test.js && eslint **/*.js.

"hoist": "all" seems too strict. Perhaps it should have the default functions value.

Or not?

Note: JSLint works the same as the all value.

https://github.com/nickdeis/eslint-plugin-no-secrets

https://eslint.org/docs/rules/no-underscore-dangle#enforceinmethodnames

https://github.com/azeemba/eslint-plugin-json

A file extension must be provided when using the import keyword. Directory indexes (e.g. './startup/index.js') must also be fully specified.

https://nodejs.org/api/esm.html#esm_mandatory_file_extensions

JSLint's rule for chained calls is different now.

The "newline-per-chained-call" rule should be disabled.

Or not?

https://github.com/mysticatea/eslint-plugin-node

https://github.com/markalfred/eslint-plugin-no-constructor-bind

https://github.com/sindresorhus/eslint-plugin-unicorn

https://github.com/bryanrsmith/eslint-plugin-sort-class-members

• Wait until class properties are part of ECMAScript

• Move eslint-config-hardcore-fp to hardcore/fp
• Add hardcore/node

One would use them like this:

{
    "extends": ["hardcore", "hardcore/fp"],
    "overrides": [
        {
            "files": ["server/**/*.js"],
            "extends": ["hardcore/node"]
        }
    ]
}

See import-js/eslint-plugin-import#1645.

TODO:

• Verify if adding plugin:import/typescript to extends can solve this (see https://github.com/benmosher/eslint-plugin-import#typescript). Update: it doesn't solve the issue, it's not related to TypeScript.

1. It may produce many false positives
2. It can't catch secrets where they are most common (configs)

https://github.com/bkucera/eslint-plugin-json-format

• Wait for kuceb/eslint-plugin-json-format#14
• Wait for a new release

There is a conflict between import/extensions, import/no-useless-path-segments, and unicorn/import-index, when referencing index files, e. g. ./index.js.

https://github.com/sarbbottam/eslint-find-rules

https://eslint.org/docs/rules/no-shadow#builtinglobals

It could be a breaking change for some codebases.

function checkAuthorization({id, pwd}) {
    // promisified

Produces: Expected line before comment. (lines-around-comment)

function checkAuthorization({id, pwd}) {

    // promisified

Produces: Block must not be padded by blank lines. (padded-blocks)

https://github.com/eslint/eslint/blob/master/conf/environments.js

• Compare https://github.com/jonaskello/eslint-plugin-functional with https://github.com/jfmengels/eslint-plugin-fp

https://github.com/freaktechnik/eslint-plugin-array-func

https://github.com/ramda/eslint-plugin-ramda

See sindresorhus/eslint-plugin-unicorn#473

• https://eslint.org/docs/rules/no-unused-vars#varsignorepattern
• https://eslint.org/docs/rules/no-unused-vars#argsignorepattern

https://github.com/nodesecurity/eslint-plugin-security

• https://github.com/EvgenyOrekhov/lints/blob/master/src/default.lints.json#L3
• EvgenyOrekhov/lints#32

https://github.com/dustinspecker/awesome-eslint

Turn on the "strict" rule when eslint/eslint#8953 is resolved.

https://github.com/sindresorhus/eslint-plugin-unicorn/blob/master/docs/rules/explicit-length-check.md#non-zero-comparisons

https://github.com/BrainMaestro/eslint-plugin-optimize-regex

The simplest way is

"preversion": "npm test",
"postversion": "git push && git push --tags && npm publish"

Investigate:

• https://github.com/semantic-release/semantic-release (aims to make releasing fully automatic)
• https://github.com/zeit/release (not standardized, the scope is limited only to publishing changelogs to GitHub releases)
• https://github.com/commitizen/cz-cli (uses an interactive prompt on commit, guides you to create a valid commit message, which is better than just throwing an "Invalid format" error; not sure how it would work for intermediate WIP-commits)
• https://github.com/conventional-changelog/commitlint
• https://github.com/jlegrone/create-semantic-module (I have enough experience to know that it's better to use the original tool than a wrapper)
• https://github.com/conventional-changelog/conventional-changelog (recommends using standard-version or semantic-release)
• https://github.com/conventional-changelog/standard-version (unlike semantic-release, it doesn't aim to fully automate the release process)
• https://github.com/changesets/changesets

https://github.com/benmosher/eslint-plugin-import

eslint/eslint#12677

There will probably be proper documentation once ESLint 7.0.0 is released.

Add ignorePatterns with "!.*". Don't forget to add default ignore patterns.

Or not?