canirequire › Dual (CommonJS + ESM) › victory-vendor
Is victory-vendor ESM-only? Can you require() it?
Vendored dependencies for Victory
Last verified Sep 9, 2026 against victory-vendor@37.3.6. JSON
Dual (CommonJS + ESM) Dual package — both require() and import work
victory-vendor publishes both a CommonJS entry and a native ESM entry (ESM added in 36.4.0). require("victory-vendor") and import "victory-vendor" both work on every supported Node.js version and in Bun.
Does victory-vendor@37.3.6 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("victory-vendor") from a CommonJS file and import "victory-vendor" from an ES module.
| Runtime | require("victory-vendor") | import "victory-vendor" |
|---|---|---|
| Node.js 18 | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED |
| Node.js 20 | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED |
| Node.js 22 | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED |
| Node.js 24 | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED |
| Node.js 26 | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED | ✗ failsERR_PACKAGE_PATH_NOT_EXPORTED |
| Bun 1.4 | ✗ failserror: Cannot find package 'victory-vendor' from '/Users/boat/Projects/top-seo/data/probe-work/victory-vendor/req.cjs' | ✗ failserror: Cannot find package 'victory-vendor' from '/Users/boat/Projects/top-seo/data/probe-work/victory-vendor/imp.mjs' |
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 victory-vendor
ES modules (import)
import victoryVendor from "victory-vendor";CommonJS (require)
const victoryVendor = require("victory-vendor");Module format by version
Derived from the type, main and exports fields of every stable release on npm (39 versions; the newest 39 shown).
| Versions | Format | First published |
|---|---|---|
| 36.4.0 – 37.3.6 | Dual (CommonJS + ESM) | May 10, 2022 |
Frequently asked
Is victory-vendor ESM-only?
victory-vendor@37.3.6 ships CommonJS and ESM builds. victory-vendor publishes both a CommonJS entry and a native ESM entry (ESM added in 36.4.0). require("victory-vendor") and import "victory-vendor" both work on every supported Node.js version and in Bun.
Can I require victory-vendor?
Yes. victory-vendor ships a CommonJS entry, so require("victory-vendor") works on every Node.js version, alongside the native ESM entry for import.
Does victory-vendor work in Bun?
Importing victory-vendor failed in Bun 1.4 on Sep 9, 2026: error: Cannot find package 'victory-vendor' from '/Users/boat/Projects/top-seo/data/probe-work/victory-vendor/imp.mjs'
Does victory-vendor ship TypeScript types?
Yes. victory-vendor bundles its own type declarations; no @types package is needed.
Links
Other dual (commonjs + esm) packages
- minimatch 10.2.6Dual
- brace-expansion 5.0.9Dual
- lru-cache 11.5.2Dual
- glob 13.0.6Dual
- eslint-visitor-keys 5.0.1Dual
- yallist 5.0.0Dual
- balanced-match 4.0.4Dual
- js-yaml 5.4.1Dual
Similar popularity
- mz 2.7.0CommonJS
- abbrev 5.0.0CommonJS
- redent 4.0.0ESM-only
- jest-environment-node 30.5.1Dual
- lie 3.3.0CommonJS
- siginfo 2.0.0CommonJS
- postcss-load-config 6.0.1CommonJS
- char-regex 2.0.2ESM-only