v0.12.2

Fixed

• Bundle analyzers work now. Added a browser field pointing at a
  dependency-free stub entry (index.browser.js) — tools like bundlephobia
  that webpack-bundle the package no longer fail on child_process and the
  platform binary packages the Node entry resolves. The stub exposes
  { version } and throws clearly if the CLI surface is called in a browser.
• Publish workflow: the crates.io "already published" check queried the local
  workspace instead of the registry (cargo info resolves workspace members
  locally), silently skipping real publishes. It now asks the sparse index.

What's Changed

• fix(release): crates.io existence check queried the local workspace, not the registry by @geaglin in #51
• release 0.12.2: browser stub entry so bundle analyzers build the package by @geaglin in #52

Full Changelog: v0.12.1...v0.12.2

Fixed

• Bundle analyzers work now. Added a browser field pointing at a
  dependency-free stub entry (index.browser.js) — tools like bundlephobia
  that webpack-bundle the package no longer fail on child_process and the
  platform binary packages the Node entry resolves. The stub exposes
  { version } and throws clearly if the CLI surface is called in a browser.
• Publish workflow: the crates.io "already published" check queried the local
  workspace instead of the registry (cargo info resolves workspace members
  locally), silently skipping real publishes. It now asks the sparse index.

What's Changed

• fix(release): crates.io existence check queried the local workspace, not the registry by @geaglin in #51
• release 0.12.2: browser stub entry so bundle analyzers build the package by @geaglin in #52

Full Changelog: v0.12.1...v0.12.2

Fixed

• Bundle analyzers work now. Added a browser field pointing at a
  dependency-free stub entry (index.browser.js) — tools like bundlephobia
  that webpack-bundle the package no longer fail on child_process and the
  platform binary packages the Node entry resolves. The stub exposes
  { version } and throws clearly if the CLI surface is called in a browser.
• Publish workflow: the crates.io "already published" check queried the local
  workspace instead of the registry (cargo info resolves workspace members
  locally), silently skipping real publishes. It now asks the sparse index.

What's Changed

• fix(release): crates.io existence check queried the local workspace, not the registry by @geaglin in #51
• release 0.12.2: browser stub entry so bundle analyzers build the package by @geaglin in #52

Full Changelog: v0.12.1...v0.12.2

Fixed

• Bundle analyzers work now. Added a browser field pointing at a
  dependency-free stub entry (index.browser.js) — tools like bundlephobia
  that webpack-bundle the package no longer fail on child_process and the
  platform binary packages the Node entry resolves. The stub exposes
  { version } and throws clearly if the CLI surface is called in a browser.
• Publish workflow: the crates.io "already published" check queried the local
  workspace instead of the registry (cargo info resolves workspace members
  locally), silently skipping real publishes. It now asks the sparse index.

What's Changed

• fix(release): crates.io existence check queried the local workspace, not the registry by @geaglin in #51
• release 0.12.2: browser stub entry so bundle analyzers build the package by @geaglin in #52

Full Changelog: v0.12.1...v0.12.2