unstale

npm / remove-markdown

remove-markdown

What changed in remove-markdown 0.6 to 0.8, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-03.

4 new APIs and options1 behavior and defaults2 tooling4 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.9 on npm

remove-markdown 0.81 changes

New APIs and options 1

  • Adds an opt-in option to remove leading MDX import blocks from excerpts; it defaults to false, preserving existing Markdown output.

    0.8.0release notes

remove-markdown 0.77 changes

New APIs and options 3

  • A self-contained ESM entry can be loaded directly by browsers and URL-based module loaders.

    0.7.0release notes

  • Deno 2 users can import the npm package directly.

    0.7.0release notes

  • Node.js ESM consumers can use a native default import while retaining the callable default API.

    0.7.0release notes

Behavior and default changes 1

  • An explicit export map provides predictable resolution for the root API, established deep imports, declarations, metadata, README, and license.

    0.7.0release notes

Tooling 1

  • CommonJS and ESM consumers receive matching module-specific TypeScript declarations.

    0.7.0release notes

Fixes and other changes 2

  • Selected tags with attributes, such as <code class="language-js">, are now preserved.

    0.7.1release notes

  • Tag matching now respects name boundaries, so selecting code does not preserve <codes>.

    0.7.1release notes

remove-markdown 0.63 changes

Tooling 1

Fixes and other changes 2