Back to Explore

wooorm/character-reference-invalid

GitHub
2 watchersOpen source

Last release:

Provides a typed ESM export, `characterReferenceInvalid`, which maps invalid HTML numeric character references to their replacement characters based on the HTML spec. Useful when parsing HTML or similar XML-like text, especially in contexts where Unicode encoding is not the primary encoding.

Project status

  • The source appears largely dormant, with the last upstream push on 2022-11-16, and no evidence of recent updates through today (2026-06-09), so active maintenance is not supported by the provided evidence.
  • Apparent update cadence is historical and infrequent, with updates in 2016 to 2021 and then a long gap after 2022-11-16; relative to today, cadence looks effectively halted.

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • 2.0.1

    Release 2.0.1 updates the project documentation and tightens TypeScript configuration for stricter typing and type coverage. The runtime surface appears largely unchanged, with the main code-level adjustment being related to how the exported map is declared and typed.

  • 2.0.0

    Release 2.0.0 switches the package to ESM and adds generated type declarations. The distribution artifact changes from a JSON entry to an exported ESM module, with updated build, test, and packaging configuration.

    BreakingFeatures
  • 1.1.4

    Release 1.1.4 is described in the notes as a prose refactor. The code diff shows the release primarily updates documentation and package metadata, plus changes to development dependencies.

  • 1.1.3

    Release 1.1.3, per the release notes, makes documentation-only updates (badges), switches some URLs to HTTPS, and renames the LICENSE file to license. The actual diff includes several non-release-noted build and tooling changes, primarily in devDependencies and the build/lint pipeline.

    Features
  • 1.1.2

    The release notes for 1.1.2 only claim a “Refactor code-style”. The code diff shows additional, non-documentation changes: devDependency and tooling upgrades, CI configuration changes, and npm scripts/build pipeline modifications that are not mentioned.

  • 1.1.1

    Release 1.1.1 updates build tooling and documentation. Release notes only mention adding a related-projects list, updating the build script, and refactoring readme.md, with no details about behavioral changes to the generated data.

    Breaking
  • 1.1.0

    Release 1.1.0 primarily removes the top-level `index.js` entrypoint and shifts the package to expose `index.json` directly. The release notes only mention this single change, but the diff shows additional build, packaging, and CI-related modifications.

    Breaking
  • 1.0.1

    Release 1.0.1 (“Rewrite module”) appears to be a tooling and packaging rewrite plus a browser bundle change. The runtime entrypoint still exports `index.json` as a mapping, but the generated browser global/UMD symbol name in the bundled artifacts changed.

  • 1.0.0

    Release 1.0.0 is listed with no accompanying release notes content. No specific features, fixes, or changes are documented in the provided information, so the upgrade impact cannot be determined from these notes alone.