This package provides a function to check whether a given Unicode code point represents a fullwidth character. It is useful for text formatting, alignment, or validation when you need to distinguish fullwidth from non-fullwidth characters.
Project status
- Actively maintained: The source shows a recent upstream push and tagged updates (v5.1.0 on 2025-08-31), but since today is 2026-09-10 there has been about a year of no further updates, so it appears not currently active and is closer to maintenance mode than active evolution.
- Update cadence (apparent): Major updates arrived at v3.0.0 (2019), v4.0.0 (2021), v5.0.0 (2023), then a smaller v5.1.0 (2025), suggesting infrequent but deliberate updates rather than a regular cadence.
AI summary generated
Recent updates
v5.1.0
v5.1.0 is described as a tree-shaking improvement. The code changes also modify the underlying width-detection logic by switching from a single helper call to two different helpers from get-east-asian-width, and it bumps the dependency version.
v5.0.0
v5.0.0 raises the minimum supported Node.js version to 18 and updates fullwidth detection to use more recent Unicode width data (via get-east-asian-width). The core implementation is no longer based on hardcoded East Asian width code point ranges.
Breakingv4.0.0
v4.0.0 marks a major release that shifts the package to a pure ESM-only distribution and raises the supported Node.js engine requirement. The core fullwidth code point logic remains largely the same, but there are subtle input validation and packaging behavior changes in the code and package metadata.
Breakingv3.0.0
This release bumps the minimum required Node.js version and adds TypeScript type definitions. No other functional changes are described in the provided release notes.
BreakingFeatures