# Is dunder-proto ESM-only? Can you require() it?

> dunder-proto@1.0.1 is a CommonJS package, reachable only through subpaths. CommonJS, subpaths only — require("dunder-proto/…") works, require("dunder-proto") does not.

If available, the `Object.prototype.__proto__` accessor and mutator, call-bound

Last verified Sep 9, 2026 against dunder-proto@1.0.1.

dunder-proto exposes only subpaths in its exports map, for example "dunder-proto/get"; there is no root entry, so require("dunder-proto") and import "dunder-proto" both throw ERR_PACKAGE_PATH_NOT_EXPORTED. The subpaths are CommonJS: require("dunder-proto/get") works everywhere, and import "dunder-proto/get" works through Node's CommonJS interop.

## What to do

1. Load subpaths, never the bare name: const dunderProto = require("dunder-proto/get"). require("dunder-proto") throws ERR_PACKAGE_PATH_NOT_EXPORTED.
2. From ES modules use the default import: import dunderProto from "dunder-proto/get"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: no types are available for dunder-proto; declare the module yourself if you need them.

## Facts

- Latest: 1.0.1 (Dec 17, 2024)
- Module format: CommonJS
- Last CommonJS version: 1.0.1
- TypeScript types: none
- Node engines: >= 0.4
- Weekly downloads: 94.0M
- License: MIT

## Runtime test results for dunder-proto@1.0.1

Installed and executed on Sep 9, 2026 with require("dunder-proto") from a CommonJS file and import "dunder-proto" from an ES module.

| Runtime | require("dunder-proto") | import "dunder-proto" |
|---|---|---|
| Node.js 18 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Node.js 20 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Node.js 22 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Node.js 24 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Node.js 26 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Bun 1.4.0 | fails (Error) | fails (Error) |

## How to import dunder-proto

ES modules:

```js
import dunderProto from "dunder-proto/get";
```

CommonJS:

```js
const dunderProto = require("dunder-proto/get");
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (2 versions; the newest 2 shown).

| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 1.0.1 | CommonJS | Dec 6, 2024 |

## Frequently asked

**Is dunder-proto ESM-only?**

dunder-proto@1.0.1 is a CommonJS package, reachable only through subpaths. dunder-proto exposes only subpaths in its exports map, for example "dunder-proto/get"; there is no root entry, so require("dunder-proto") and import "dunder-proto" both throw ERR_PACKAGE_PATH_NOT_EXPORTED. The subpaths are CommonJS: require("dunder-proto/get") works everywhere, and import "dunder-proto/get" works through Node's CommonJS interop.

**Can I require dunder-proto?**

Only by subpath. require("dunder-proto") throws ERR_PACKAGE_PATH_NOT_EXPORTED because the exports map has no root entry; require("dunder-proto/get") works.

**Can I import dunder-proto with ES module syntax?**

Yes. import dunderProto from "dunder-proto/get" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.

**Does dunder-proto work in Bun?**

Importing dunder-proto failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find package 'dunder-proto' from '/Users/boat/Projects/top-seo/data/probe-work/dunder-proto/imp.mjs'

**Does dunder-proto ship TypeScript types?**

No. dunder-proto ships no type declarations and there is no @types package for it.

## Links

- [dunder-proto on npm](https://www.npmjs.com/package/dunder-proto)
- [Source repository](https://github.com/es-shims/dunder-proto)
- [HTML version](https://canirequire.com/package/dunder-proto/)
- [JSON version](https://canirequire.com/package/dunder-proto.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.