Skip to content

[Content] The need to require a Node.js version is not specified in JavaScript GuidelinesΒ #666

@possumbilities

Description

@possumbilities

Problem

Currently there is not a consistent method across repositories for requiring a minimum Node.js version. This can and will create issues for contributing to repositories.

Description

This can be solved by adding guidance in the Javascript Guidelines to add:

"engines" : { "npm" : ">=x.y.z","node" : ">=x.yz"} to the package.json file as a baseline standard

Alternatives

Additionally, you can edit the .npmrc file to contain:

# .npmrc
engine-strict=true

but this provides inconsistent behavior, as local devs may have their own pre-existing .npmrc file.

A .nvmrc route is also possible and might have better outcomes

Additional context

Implementation

  • I would be interested in implementing this feature.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions