typesPresence

Enforces that the types property is present.

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

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

Examples

❌ Incorrect

{}

{
  "name": "my-repository"
}

✅ Correct

{
  "types": "./index.d.ts"
}

{
  "name": "my-repository",
  "types": "./index.d.ts"
}

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 generates .d.t.s files only in locations TypeScript will automatically detect, or does not publish TypeScript declarations, you can disable this rule. Most projects generally don’t need this rule because sibling declarations are inferred from the file structure. Alternately, a non-public JavaScript-only package without declaration files may not need a types field or types at all.

Related Rules

• mainPresence - Enforces that the main property is present.
• modulePresence - Enforces that the module property is present.

Further Reading

• npm: package.json > types

Equivalents in Other Linters

• ESLint: package-json/require-types