Vigia

Upgrading emojibase-regex from 17.x to 18.x

Comparison of the public API of emojibase-regex 17.0.0 and 18.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths0
Removed exports0
Changed signatures0
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)0
New exports0

Removed exports

None detected.

Changed signatures

None detected.

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

None detected.

Changelog between these versions

Text published by the package authors, shown as-is.

18.0.0
### Major Changes

- 8527c93: Update to Emoji v18 and CLDR 49 (beta 1), following UTS #51 revision 31. Adds 9 emoji (🫫 🫹 🫺 🫌 🫝 🛙 🪋
  🪌 🪍), with skin tones for the two thumb signs, and their localized labels and keywords.

### Minor Changes

- 06b8716: Align presentation and qualification with UTS #51:
  
  - The `emoji` field is now the fully-qualified form from `emoji-test.txt`. 152 emoji that default to
    emoji presentation, like 👍 and ⌚, no longer have a redundant `FE0F`.
  - `meta/hexcodes.json` now lists statuses exactly as `emoji-test.txt` does. Text presentation
    sequences (`FE0E`) and redundant `FE0F` forms are no longer listed as fully qualified, and the
    skin tone and hair components are listed with the new `COMPONENT` qualifier.
  - The `emojibase-regex/emoji` pattern now matches default-emoji characters without `FE0F`.
- 06b8716: Match emoji by presentation and qualification, as UTS #51 defines them:
  
  - `emoji-loose` now matches every minimally-qualified and unqualified form, such as 🕵‍♂.
  - `text` now matches emoji that default to text presentation without `FE0E`, such as a bare ©.
  - `text-loose` no longer matches sequences or emoji without a text presentation form, such as 🇺🇸.
  - The emoji and text patterns no longer match a character that a selector or skin tone puts in the
    other presentation, such as the ⚠ in ⚠️.
  - The `property` patterns now define the `u` flag and actually match emoji: possible emoji,
    fully-qualified emoji, and emoji in text presentation.

Give your AI agent these facts

Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.

claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp

Add to CursorAdd to VS Code★ Star on GitHub

Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }

Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests

Frequently asked questions

What are the breaking changes when upgrading emojibase-regex from 17 to 18?

Between emojibase-regex 17.0.0 and 18.0.0, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.

What became deprecated in emojibase-regex 18?

0 exports or members are newly marked as deprecated in emojibase-regex 18.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/emojibase-regex/upgrade?from=17.0.0&to=18.0.0