canirequire › CommonJS › @istanbuljs/nyc-config-typescript
Is @istanbuljs/nyc-config-typescript ESM-only? Can you require() it?
nyc configuration that works with typescript
Last verified Sep 9, 2026 against @istanbuljs/nyc-config-typescript@1.0.2. JSON
CommonJS CommonJS — require() works on every Node.js version
@istanbuljs/nyc-config-typescript ships CommonJS only. require("@istanbuljs/nyc-config-typescript") works everywhere. import "@istanbuljs/nyc-config-typescript" 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.
Does @istanbuljs/nyc-config-typescript@1.0.2 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@istanbuljs/nyc-config-typescript") from a CommonJS file and import "@istanbuljs/nyc-config-typescript" from an ES module.
| Runtime | require("@istanbuljs/nyc-config-typescript") | import "@istanbuljs/nyc-config-typescript" |
|---|---|---|
| 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 | ✓ works | ✓ works |
How to import @istanbuljs/nyc-config-typescript
ES modules (import)
import nycConfigTypescript from "@istanbuljs/nyc-config-typescript";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
const nycConfigTypescript = require("@istanbuljs/nyc-config-typescript");Module format by version
Derived from the type, main and exports fields of every stable release on npm (7 versions; the newest 7 shown).
| Versions | Format | First published |
|---|---|---|
| 0.1.0 – 1.0.2 | CommonJS | Jan 29, 2019 |
Frequently asked
Is @istanbuljs/nyc-config-typescript ESM-only?
@istanbuljs/nyc-config-typescript@1.0.2 is a CommonJS package. @istanbuljs/nyc-config-typescript ships CommonJS only. require("@istanbuljs/nyc-config-typescript") works everywhere. import "@istanbuljs/nyc-config-typescript" 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 @istanbuljs/nyc-config-typescript with ES module syntax?
Yes. import nycConfigTypescript from "@istanbuljs/nyc-config-typescript" 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 @istanbuljs/nyc-config-typescript work in Bun?
Yes. import "@istanbuljs/nyc-config-typescript" loaded successfully in Bun 1.4 on Sep 9, 2026.
Does @istanbuljs/nyc-config-typescript ship TypeScript types?
No. @istanbuljs/nyc-config-typescript ships no type declarations and there is no @types package for it.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- @angular/platform-server 22.1.5ESM-only
- @storybook/addon-knobs 8.0.1No entry
- @vue/cli-service 5.0.9CommonJS
- @vue/cli-plugin-router 5.0.9CommonJS
- @vue/cli-plugin-babel 5.0.9CommonJS
- @tsconfig/recommended 1.0.13CommonJS
- @svgr/rollup 8.1.0CommonJS
- @storybook/addon-storysource 8.6.14Dual