canirequire › No JS entry point › @octokit/openapi-types
Is @octokit/openapi-types ESM-only? Can you require() it?
Generated TypeScript definitions based on GitHub's OpenAPI spec for api.github.com
Last verified Sep 9, 2026 against @octokit/openapi-types@29.0.1. Markdown · JSON
No JS entry point No JavaScript entry point
@octokit/openapi-types 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 @octokit/openapi-types: it has no JavaScript entry point. Use it as a CLI (npx @octokit/openapi-types), a stylesheet, an asset, or a type-definition package as its README describes.
- TypeScript: types are bundled; install nothing extra.
Does @octokit/openapi-types@29.0.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@octokit/openapi-types") from a CommonJS file and import "@octokit/openapi-types" from an ES module.
| Runtime | require("@octokit/openapi-types") | import "@octokit/openapi-types" |
|---|---|---|
| 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 @octokit/openapi-types
ES modules (import)
import * as openapiTypes from "@octokit/openapi-types";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 (162 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 12.7.0 – 29.0.1 | No JS entry point | Jul 4, 2022 |
Frequently asked
Is @octokit/openapi-types ESM-only?
@octokit/openapi-types@29.0.1 has no importable main entry. @octokit/openapi-types 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 @octokit/openapi-types work in Bun?
Importing @octokit/openapi-types failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module '@octokit/openapi-types' from '/Users/boat/Projects/top-seo/data/probe-work/@octokit__openapi-types/imp.mjs'
Does @octokit/openapi-types ship TypeScript types?
Yes. @octokit/openapi-types bundles its own type declarations; no @types package is needed.
Links
Other no js entry point packages
- type-fest 5.9.0No entry
- undici-types 8.10.2No entry
- node-releases 2.0.55No entry
- pnpm 12.3.4No entry
- csstype 3.2.3No entry
- @eslint/core 1.2.1No entry
- @octokit/types 18.0.0No entry
- @openai/codex 0.153.4No entry
Similar popularity
- lodash.debounce 4.0.8CommonJS
- pino 10.3.1CommonJS
- jest-runner 30.5.1Dual
- expect 30.5.1Dual
- serialize-javascript 7.1.1CommonJS
- nwsapi 2.2.27CommonJS
- jest-leak-detector 30.5.1Dual
- @babel/plugin-syntax-import-attributes 7.29.7CommonJS