Back to Explore

inspect-js/is-core-module

GitHub
1 updates · last 90 days1 watchersOpen source

Last release: 4 weeks ago

`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 signals: the upstream shows a very recent push (2026-05-05), and an update was published shortly before that (v2.16.2 on 2026-05-05), indicating ongoing work rather than abandonware.
  • Apparent update cadence: after v2.16.0 and v2.16.1 in mid to late December 2024, the next documented update is v2.16.2 in May 2026, which suggests a low-frequency cadence with occasional batches rather than regular releases.

AI summary generated Today

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

Recent updates

  • v2.16.2

    4 weeks ago

    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

    12/21/2024

    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

    12/13/2024

    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.