chore: bump version.

Author: knightedcodemonkey

docs/roadmap.md

@@ -2,36 +2,38 @@
 
 Status: draft
 
-## Pretty Output Mode
+## Idiomatic Exports Mode (aka `pretty`)
 
-Goal: Add an opt-in `pretty` (aka `idiomaticExports`) mode to reduce synthesized helper bags when converting between CJS and ESM.
+Goal: Add an opt-in `idiomaticExports` (current shorthand: `pretty`) mode to reduce synthesized helper bags when converting between CJS and ESM. Primary motivation: produce more idiomatic ESM output that is easier for bundlers to tree-shake when inputs qualify for the “safe” path.
 
 ### CJS → ESM
 
-- Option: `pretty: 'safe' | 'aggressive'` (default: off).
+- Option: `pretty: 'safe' | 'aggressive'` (default: off). Consider exposing the option as `idiomaticExports` to better signal the intent and tree-shaking upside.
 - Safe mode rules (emit direct exports, avoid `__exports` when all are true):
   - Only top-level `exports.*` writes or a single `module.exports = { ... }` / `module.exports = fn`.
   - No reassignments after initial writes; no getters/setters; no computed/non-identifier keys; no mixed `exports` + `module.exports` unless we can rewrite deterministically.
   - No shadowed `module`/`exports`; no top-level `return`; no `require.cache/extensions`; no dynamic require inside export initializers; no TDZ hazards.
 - Aggressive mode: allow mixed exports + `module.exports` if we can derive both default and named exports; allow identifier-safe computed keys; allow a single reassignment.
-- Emission strategy:
+- Emission strategy (tree-shake-friendly when rules pass):
   - Named writes → `export const foo = ...` or `export { local as foo }`.
   - `module.exports = { ... }` → `export default { ... }` (+ optional named re-exports for plain identifiers if a sub-option is enabled).
   - `module.exports = fn` → `export default fn`.
   - Fallback to `__exports` when rules fail.
+- Tree shaking note: Safe mode outputs static `export` forms, which typical bundlers can eliminate when unused. Aggressive mode may reintroduce helper bags or conservative shapes, so shaking benefits are best-effort there.
 - Diagnostics: warn when `pretty` requested but fell back; warn when live-binding fidelity may differ in aggressive mode.
 - Tests: fixture matrix (safe object, safe function default, mixed exports+module.exports, computed keys, reassignments) with assertions on generated text (absence/presence of `__exports`) and runtime behavior.
 
 ### ESM → CJS
 
-- Option: same `pretty` flag, but constrained by live bindings and TLA.
+- Option: same `pretty`/`idiomaticExports` flag, but constrained by live bindings and TLA.
 - Preconditions for pretty CJS:
   - `topLevelAwait === 'error'` or known-wrap path; `liveBindings !== 'strict'` (or accept relaxed semantics in aggressive mode).
   - No namespace exports requiring live getters; no export-all with live needs unless we accept relaxed semantics.
 - Emission strategy when safe:
   - Direct `exports.foo = foo;` and `module.exports = default` without namespace helpers.
   - Avoid namespace helper when `export * as ns` can map to `const ns = require(...); exports.ns = ns;` under relaxed live-binding semantics.
   - Keep helpers for TLA wrap and strict live bindings.
+- Tree shaking note: CJS output is inherently not statically tree-shakeable; “pretty” here is mostly about readability/minimal helpers rather than true shakeability.
 - Tests: fixtures verifying helper-free output under safe conditions and fallback when constraints are present.
 
 ## Documentation & UX

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@knighted/module",
-  "version": "1.0.0-rc.4",
+  "version": "1.0.0-rc.5",
   "description": "Transforms differences between ES modules and CommonJS.",
   "type": "module",
   "main": "dist/module.js",