Skip to content

Address problems with package.json inspection #163

Closed
@marcelklehr

Description

See #162 for one instance of the problems caused by relying on the engines field. (If only people would be careful about what they put there...) I tend to think that being that clever is actually a good thing, as it theoretically allows you to run any globally installed npm packages without caring about which node version they need. Perhaps there should be an option to enable/disable this feature :)

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions