Skip to content

Add eslint rules to avoid usage of unsupported node features? #190

Description

@karfau

@XhmikosR suggested to make use of some of these eslint rules: https://github.com/mysticatea/eslint-plugin-node
Which work based on the engines field in package.json.

We are already using the eslint-plugin-es5, we should check if there is an overlap and if it makes sense, since node is not our only supported environment.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions