`is-core-module` checks whether a given module specifier refers to a Node.js core module, optionally using a specific Node.js version (defaults to the current version). It is useful in Node tooling and libraries that need to branch logic based on whether a dependency is built into Node or comes from userland.
Project status
- Actively maintained, with an upstream push and v2.18.0 update on 2026-11-03.
- Updates have been irregular, with a long gap from December 2024 to May 2026, followed by updates in September and November 2026.
AI summary generated
Recent updates
v2.18.0
The publisher provided no release notes for v2.18.0. The code updates the core-module database for Node.js 27, recognizing new module specifiers and stopping recognition of two private TLS modules; the repository CHANGELOG records these changes, but they are absent from the publisher-provided notes.
BreakingFeaturesv2.17.0
v2.17.0 primarily adds first-party TypeScript typings for `isCore`, including a typed `isCore.Module` union derived from `core.json`. It also updates the underlying core-module dataset to include `node:ffi` availability (Node >= 26.9), alongside various dev tooling and CI workflow adjustments.
BreakingFeaturesv2.16.2
v2.16.2 primarily updates the internal core module version map, especially for Node 26 behavior around _stream_* modules. The release also updates CI workflow permissions and test coverage, with dependency bumps (hasown) and various dev tooling updates.
v2.16.1
No publisher release notes were provided for v2.16.1. The actual changes in this release are limited to metadata and core module availability rules, specifically adjusting the Node version range for `node:sqlite`.
v2.16.0
Release v2.16.0 was published on 2024-12-13. No release notes were provided by the publisher, so there is no described information about features, fixes, breaking changes, security updates, or migrations. Developers should review the changelog, compare tags, or inspect the diff between v2.15.x and v2.16.0 to identify any undocumented changes.
v2.15.1
Release v2.15.1 contains no release-note content from the publisher, but the code diff shows changes in test coverage and package configuration. The only likely runtime-impacting change is an update to core.json that adjusts version ranges for the Node core specifier `test/mock_loader` (and `node:test/mock_loader`).
v2.15.0
Release v2.15.0 of is-core-module adds recognition for the Node.js core module specifier node:sea for specific Node.js version ranges. The code changes also update the test suite and the repository changelog to reflect this new supported module.
Featuresv2.14.0
v2.14.0 mainly updates project metadata and test-related requirements, with version bumps and dependency updates. The core behavioral change appears to be expanding the set of Node.js built-in specifiers recognized as core modules, adding support for `test/mock_loader` and `node:test/mock_loader`.
v2.13.1
v2.13.1 is a small maintenance release with no functional feature notes provided. The code changes are primarily a dependency swap from `has` to `hasown`, plus minor dev dependency updates, and the package version is bumped to 2.13.1.
v2.13.0
v2.13.0 bumps the package version and updates the Node version ranges used to classify certain module specifiers as core modules. The only substantive change in the diff is in core.json, adjusting support detection ranges for node:test/reporters and wasi/node:wasi. Dev dependencies were also incremented.
v2.12.1
Release v2.12.1 updates the module-specifier/version mapping for Node.js core modules. The only functional change is tightening support for the specifier `test/reporters`, reflecting that Node v20.2+ requires the `node:` prefix for that specifier.
v2.12.0
Release v2.12.0 was published on 2023-04-10. No release notes were provided, so the changes in this version are not described and developer impact cannot be determined from the publisher’s documentation.