canirequire › No JS entry point › jsdoc
Is jsdoc ESM-only? Can you require() it?
An API documentation generator for JavaScript.
Last verified Sep 9, 2026 against jsdoc@4.0.5. Markdown · JSON
No JS entry point No JavaScript entry point
jsdoc 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 jsdoc: it has no JavaScript entry point. Use it as a CLI (npx jsdoc), a stylesheet, an asset, or a type-definition package as its README describes.
- TypeScript: no types are available for jsdoc; declare the module yourself if you need them.
Does jsdoc@4.0.5 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("jsdoc") from a CommonJS file and import "jsdoc" from an ES module.
| Runtime | require("jsdoc") | import "jsdoc" |
|---|---|---|
| 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 jsdoc
ES modules (import)
import * as jsdoc from "jsdoc";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 (36 versions; the newest 36 shown).
| Versions | Format | First published |
|---|---|---|
| 3.2.0 – 4.0.5 | No JS entry point | Jun 24, 2013 |
| 0.0.0 | CommonJS | Sep 19, 2011 |
Frequently asked
Is jsdoc ESM-only?
jsdoc@4.0.5 has no importable main entry. jsdoc 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 jsdoc work in Bun?
Importing jsdoc failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find package 'jsdoc' from '/Users/boat/Projects/top-seo/data/probe-work/jsdoc/imp.mjs'
Does jsdoc ship TypeScript types?
No. jsdoc 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
- 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
- @octokit/openapi-types 29.0.1No entry
Similar popularity
- bunyan 1.8.15CommonJS
- karma-chrome-launcher 3.2.0CommonJS
- @semantic-release/commit-analyzer 13.0.1ESM-only
- optimist 0.6.1CommonJS
- stylus 0.64.0CommonJS
- babel-plugin-named-asset-import 0.3.8CommonJS
- @angular-devkit/build-angular 22.1.7CommonJS
- eslint-config-standard 17.1.0CommonJS