# Is xml-name-validator ESM-only? Can you require() it?

> xml-name-validator@5.0.0 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

Validates whether a string matches the production for an XML name or qualified name

Last verified Sep 9, 2026 against xml-name-validator@5.0.0.

xml-name-validator ships CommonJS only. require("xml-name-validator") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18. import "xml-name-validator" 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("xml-name-validator") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18.
2. From ES modules use the default import: import xmlNameValidator from "xml-name-validator"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: npm install -D @types/xml-name-validator

## Facts

- Latest: 5.0.0 (Nov 12, 2023)
- Module format: CommonJS
- Last CommonJS version: 5.0.0
- TypeScript types: @types/xml-name-validator
- Node engines: >=18
- Weekly downloads: 66.3M
- License: Apache-2.0

## Runtime test results for xml-name-validator@5.0.0

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

| Runtime | require("xml-name-validator") | import "xml-name-validator" |
|---|---|---|
| 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 xml-name-validator

ES modules:

```js
import xmlNameValidator from "xml-name-validator";
```

CommonJS:

```js
const xmlNameValidator = require("xml-name-validator");
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 5.0.0 | CommonJS | Dec 28, 2014 |

## Frequently asked

**Is xml-name-validator ESM-only?**

xml-name-validator@5.0.0 is a CommonJS package. xml-name-validator ships CommonJS only. require("xml-name-validator") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18. import "xml-name-validator" 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 xml-name-validator with ES module syntax?**

Yes. import xmlNameValidator from "xml-name-validator" 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 xml-name-validator work in Bun?**

Yes. import "xml-name-validator" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does xml-name-validator ship TypeScript types?**

Not bundled. Install the community types with "npm install -D @types/xml-name-validator".

## Links

- [xml-name-validator on npm](https://www.npmjs.com/package/xml-name-validator)
- [Source repository](https://github.com/jsdom/xml-name-validator)
- [HTML version](https://canirequire.com/package/xml-name-validator/)
- [JSON version](https://canirequire.com/package/xml-name-validator.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.