node-exports-info provides information about which Node.js versions support the `exports` field, including version ranges and categories for features like conditions, patterns, and pattern trailers. It is useful for tooling that needs to decide how `exports` should be interpreted for a given Node version, and includes helper functions to map semver ranges to supported categories and flags.
Project status
- The source appears actively maintained, with multiple tagged updates on 2026-01-28 (v1.6.0 and v1.5.1), and an additional update on 2026-01-16 (v1.5.0), indicating ongoing development.
- The apparent update cadence is relatively frequent in late January 2026, with changes spanning roughly 12 days from v1.5.0 to v1.5.1, and then another update the same day (v1.5.1 to v1.6.0).
AI summary generated Today
Recent updates
v1.6.0
4 months agov1.6.0 adds two new public entry points, getCategoryFlags and getCategoryInfo, plus corresponding TypeScript declarations and tests. The diff also updates README and CHANGELOG formatting, but does not show any removal or modification of existing APIs.
Featuresv1.5.1
4 months agov1.5.1 is primarily a types-related patch release. The only code changes are in TypeScript declaration files and changelog/version metadata, with no runtime logic changes shown in the diff.
v1.5.0
4 months agoRelease v1.5.0 was published on 2026-01-16, but no release notes or change log details were provided in the available data. As a result, the API compatibility, breaking changes, and bug/security/performance impact cannot be determined from the release notes.
v1.4.0
4 months agov1.4.0 expands the library's Node.js exports capability detection by adding new categories and version ranges related to require(esm), JSON imports, and automatic type stripping from TypeScript sources. The implementation also refactors internals to use simple loops instead of array.prototype.find, and it switches to es-errors for RangeError and TypeError construction. No release notes were provided by the publisher, so the documented behavior change surface is unclear.
Featuresv1.3.1
2/26/2024v1.3.1 appears to primarily add TypeScript type declarations for the package API, along with repo tooling updates (TypeScript typechecking in lint, and small CI workflow adjustments). The provided release notes are empty, so the documented vs actual change comparison mainly indicates most changes are undocumented.
Featuresv1.3.0
12/15/2023This release (v1.3.0) adds a new API function, isCategory, intended to validate whether a provided value is a known exports category. The published package entrypoints (package.json exports map) and documentation (README) are updated accordingly, along with new unit tests.
v1.2.1
12/15/2023Version bump to v1.2.1 with mostly maintenance changes. The code changes primarily adjust how the npm package is built and published (npmignore autogeneration and publish safeguards), alongside small dependency bumps and a robustness tweak in ranges.js.
Breakingv1.2.0
4/9/2022v1.2.0 introduces an enhancement to `getConditionsForCategory` to support module-system specific condition sets, and updates related tests and documentation. The release also modifies multiple GitHub Actions workflows, tightening job permissions and switching to reusable/composable workflows, and bumps the `tape` dev dependency.
BreakingSecurityFeaturesv1.1.3
3/25/2022v1.1.3 bumps the package version and updates the documented and implemented Node version ranges for categorizing `exports` support behavior. The only functional changes in the diff are to the version range mappings (not new runtime APIs).
v1.1.2
3/22/2022Release v1.1.2 was published on 2022-03-22, but the publisher did not provide release notes. No documented changes, bug fixes, security updates, or migration steps are available in the provided data.