# Is is-string ESM-only? Can you require() it?

> is-string@1.1.1 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

Is this value a JS String object or primitive? This module works cross-realm/iframe, and despite ES6 @@toStringTag.

Last verified Sep 9, 2026 against is-string@1.1.1.

is-string ships CommonJS only. require("is-string") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4. import "is-string" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

## What to do

1. require("is-string") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4.
2. From ES modules use the default import: import isString from "is-string"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 1.1.1 (Dec 16, 2024)
- Module format: CommonJS
- Last CommonJS version: 1.1.1
- TypeScript types: bundled
- Node engines: >= 0.4
- Weekly downloads: 79.2M
- License: MIT

## Runtime test results for is-string@1.1.1

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

| Runtime | require("is-string") | import "is-string" |
|---|---|---|
| Node.js 18 | works | works |
| Node.js 20 | works | works |
| Node.js 22 | works | works |
| Node.js 24 | works | works |
| Node.js 26 | works | works |
| Bun 1.4.0 | works | works |

## How to import is-string

ES modules:

```js
import isString from "is-string";
```

CommonJS:

```js
const isString = require("is-string");
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 1.1.1 | CommonJS | Jan 29, 2015 |

## Frequently asked

**Is is-string ESM-only?**

is-string@1.1.1 is a CommonJS package. is-string ships CommonJS only. require("is-string") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4. import "is-string" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

**Can I import is-string with ES module syntax?**

Yes. import isString from "is-string" 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 is-string work in Bun?**

Yes. import "is-string" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does is-string ship TypeScript types?**

Yes. is-string bundles its own type declarations; no @types package is needed.

## Links

- [is-string on npm](https://www.npmjs.com/package/is-string)
- [Source repository](https://github.com/inspect-js/is-string)
- [HTML version](https://canirequire.com/package/is-string/)
- [JSON version](https://canirequire.com/package/is-string.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.