exportsSubpathsStyle

Enforce consistent root exports subpath style in package.json.

✅ This rule is included in the package-json stylistic presets.

The Node.js exports field allows a single root export to be written as a direct value or under the "." subpath. Both forms resolve the package root, but using one style consistently keeps package manifests easier to compare.

By default, this rule prefers the explicit "." subpath form. The explicit form keeps the top-level exports shape stable if the package later adds additional subpaths.

Examples

❌ Incorrect

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

{
  "exports": {
    "import": "./index.mjs",
    "require": "./index.cjs"
  }
}

✅ Correct

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

{
  "exports": {
    ".": {
      "import": "./index.mjs",
      "require": "./index.cjs"
    }
  }
}

{
  "exports": {
    ".": "./index.js",
    "./utils": "./utils.js"
  }
}

Options

prefer

Type: "explicit" | "implicit"

Default: "explicit"

Which single root export style to enforce. Use "explicit" to require the "." subpath wrapper. Use "implicit" to prefer the direct root export value when no other subpaths are present.

packageJson.rules({
  exportsSubpathsStyle: {
    prefer: "implicit",
  },
});

With "implicit", this rule does not unwrap exports objects that declare more than the root subpath. Multiple package subpaths require the explicit object form.

When Not To Use It

If your project does not use exports, or your package manifests intentionally mix both single-root forms to match generated output from another tool, this rule may not be useful for that package.

Further Reading

• Node.js: Package entry points
• Node.js: Subpath exports

Equivalents in Other Linters

• ESLint: package-json/exports-subpaths-style