# Is node-releases ESM-only? Can you require() it?

> node-releases@2.0.55 has no importable main entry. No JavaScript entry point.

Node.js releases data

Last verified Sep 9, 2026 against node-releases@2.0.55.

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

1. 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.
2. TypeScript: no types are available for node-releases; declare the module yourself if you need them.

## Facts

- Latest: 2.0.55 (Sep 9, 2026)
- Module format: No JS entry point
- Last CommonJS version: n/a
- TypeScript types: none
- Node engines: >=18
- Weekly downloads: 164.1M
- License: MIT

## Runtime test results for node-releases@2.0.55

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 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Node.js 20 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Node.js 22 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Node.js 24 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Node.js 26 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Bun 1.4.0 | fails (Error) | fails (Error) |

## How to import node-releases

ES modules:

```js
import * as nodeReleases from "node-releases";
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (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

- [node-releases on npm](https://www.npmjs.com/package/node-releases)
- [Source repository](https://github.com/chicoxyzzy/node-releases)
- [HTML version](https://canirequire.com/package/node-releases/)
- [JSON version](https://canirequire.com/package/node-releases.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.