Normalize Bundler

Normalize types, module, sideEffects, and esnext bundler convention fields in workspace package.json files.

Summary

The normalize-bundler recipe handles unofficial bundler convention fields in each workspace's package.json.

It merges the deprecated typings field into types, and normalizes module, sideEffects, and esnext fields according to common bundler expectations.

Why Use This Command?

1. Keeps bundler convention fields aligned with workspace roles that can actually use them.
2. Merges the legacy typings field safely into types so declarations have one source.
3. Removes empty or inapplicable fields before they confuse package consumers and tooling.

Requirements

• Node.js runtime — Use a supported Node.js LTS release with the Nova CLI available.
• Project config — Register the workspace and enable recipes.package-json.<workspace>.normalize-bundler in nova.config.json.
• Workspace manifest — The configured workspace must contain a readable package.json file.

Behavior

For each eligible workspace, the recipe inspects bundler convention fields and applies the following rules. See Workspace Rules for how tags are determined.

• typings → types merge (Conditional) — If both fields exist, the existing types value is kept and typings is deleted. If only typings exists, it is renamed to types.
• types (Conditional) — Removed if the workspace role does not allow it (only config, package, and tool roles retain this field).
• module (Conditional) — Removed if the workspace role does not allow it (only config, package, and tool roles retain this field).
• sideEffects (Conditional) — Removed if the workspace role does not allow it (only package roles retain this field).
• esnext (Conditional) — Removed if the workspace role does not allow it (only package roles retain this field).

Usage

Options