modulePresence

Enforces that the module property is present.

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

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

Examples

❌ Incorrect

{}

{
  "name": "my-repository"
}

✅ Correct

{
  "module": "./index.js"
}

{
  "module": "./index.js",
  "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 publish a separate ES module entry point, you can disable this rule. For example, a package that uses exports for all entry points may not need a module field.

Related Rules

• moduleValidity - Enforces that the module property is valid.

Further Reading

• Node.js: Package entry points

Equivalents in Other Linters

• ESLint: package-json/require-module