devEnginesPresence

Enforces that the devEngines property is present.

✅ This rule is included in the package-json preset.

This rule requires the devEngines field in package.json to be present.

Examples

❌ Incorrect

{}

{
  "name": "my-repository"
}

✅ Correct

{
  "devEngines": {
    "runtime": {
      "name": "node"
    }
  }
}

{
  "devEngines": {
    "runtime": {
      "name": "node"
    }
  },
  "name": "my-repository"
}

Options

ignorePrivate

Whether the property should still be required when the package’s private property is true. Defaults to false.

This option can be useful if the rule is enabled on many package.json files and some files differ in privacy.

When Not To Use It

If your package does not need to constrain contributor development tooling, you can disable this rule. For example, a package maintained by one team in a controlled environment may not need devEngines metadata.

Related Rules

• devEnginesValidity - Enforces that the devEngines property is valid.

Further Reading

• npm: package.json > devEngines

Equivalents in Other Linters

• ESLint: package-json/require-devEngines