canirequire › No JS entry point › node-releases
Is node-releases ESM-only? Can you require() it?
Node.js releases data
Last verified Sep 9, 2026 against node-releases@2.0.55. Markdown · JSON
No JS entry point No JavaScript entry point
node-releases does not expose a JavaScript entry point in package.json. It is likely a CLI, a stylesheet, a type-definition package, or an asset bundle, so require() and import are not the way to use it.
What to do
- Do not require() or import node-releases: it has no JavaScript entry point. Use it as a CLI (npx node-releases), a stylesheet, an asset, or a type-definition package as its README describes.
- TypeScript: no types are available for node-releases; declare the module yourself if you need them.
Does node-releases@2.0.55 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("node-releases") from a CommonJS file and import "node-releases" from an ES module.
| Runtime | require("node-releases") | import "node-releases" |
|---|---|---|
| Node.js 18 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 20 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 22 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 24 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 26 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Bun 1.4.0 | ✗ failsError | ✗ failsError |
A failing require() on a CommonJS package usually means the package needs a browser/DOM global, a peer dependency, or a native binary that is not available in a bare Node.js process.
How to import node-releases
ES modules (import)
import * as nodeReleases from "node-releases";CommonJS (require)
Not applicable.
Module format by version
Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (121 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 1.1.57 – 2.0.55 | No JS entry point | May 27, 2020 |
Frequently asked
Is node-releases ESM-only?
node-releases@2.0.55 has no importable main entry. node-releases does not expose a JavaScript entry point in package.json. It is likely a CLI, a stylesheet, a type-definition package, or an asset bundle, so require() and import are not the way to use it.
Does node-releases work in Bun?
Importing node-releases failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find package 'node-releases' from '/Users/boat/Projects/top-seo/data/probe-work/node-releases/imp.mjs'
Does node-releases ship TypeScript types?
No. node-releases ships no type declarations and there is no @types package for it.
Links
Other no js entry point packages
- type-fest 5.9.0No entry
- undici-types 8.10.2No entry
- pnpm 12.3.4No entry
- csstype 3.2.3No entry
- @eslint/core 1.2.1No entry
- @octokit/types 18.0.0No entry
- @octokit/openapi-types 29.0.1No entry
- @openai/codex 0.153.4No entry
Similar popularity
- @babel/template 8.0.0ESM-only
- has-flag 5.0.1ESM-only
- qs 6.16.0CommonJS
- @jridgewell/resolve-uri 3.1.2Dual
- @jridgewell/gen-mapping 0.3.13Dual
- onetime 8.0.0ESM-only
- fdir 6.5.0Dual
- pnpm 12.3.4No entry