canirequire › CommonJS › @tsconfig/recommended
Is @tsconfig/recommended ESM-only? Can you require() it?
A base TSConfig for working with Recommended.
Last verified Sep 9, 2026 against @tsconfig/recommended@1.0.13. JSON
CommonJS CommonJS — require() works on every Node.js version
@tsconfig/recommended ships CommonJS only. require("@tsconfig/recommended") works everywhere. import "@tsconfig/recommended" 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 @tsconfig/recommended@1.0.13 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@tsconfig/recommended") from a CommonJS file and import "@tsconfig/recommended" from an ES module.
| Runtime | require("@tsconfig/recommended") | import "@tsconfig/recommended" |
|---|---|---|
| Node.js 18 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 20 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 22 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 24 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 26 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Bun 1.4 | ✗ failserror: Cannot find module '@tsconfig/recommended' from '/Users/boat/Projects/top-seo/data/probe-work/@tsconfig__recommended/req.cjs' | ✗ failserror: Cannot find module '@tsconfig/recommended' from '/Users/boat/Projects/top-seo/data/probe-work/@tsconfig__recommended/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 @tsconfig/recommended
ES modules (import)
import recommended from "@tsconfig/recommended";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 recommended = require("@tsconfig/recommended");Module format by version
Derived from the type, main and exports fields of every stable release on npm (14 versions; the newest 14 shown).
| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 1.0.13 | CommonJS | Aug 6, 2020 |
Frequently asked
Is @tsconfig/recommended ESM-only?
@tsconfig/recommended@1.0.13 is a CommonJS package. @tsconfig/recommended ships CommonJS only. require("@tsconfig/recommended") works everywhere. import "@tsconfig/recommended" 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 @tsconfig/recommended with ES module syntax?
Yes. import recommended from "@tsconfig/recommended" 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 @tsconfig/recommended work in Bun?
Importing @tsconfig/recommended failed in Bun 1.4 on Sep 9, 2026: error: Cannot find module '@tsconfig/recommended' from '/Users/boat/Projects/top-seo/data/probe-work/@tsconfig__recommended/imp.mjs'
Does @tsconfig/recommended ship TypeScript types?
No. @tsconfig/recommended 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
- @vue/cli-service 5.0.9CommonJS
- @vue/cli-plugin-router 5.0.9CommonJS
- @istanbuljs/nyc-config-typescript 1.0.2CommonJS
- @vue/cli-plugin-babel 5.0.9CommonJS
- @svgr/rollup 8.1.0CommonJS
- @storybook/addon-storysource 8.6.14Dual
- @vue/cli-plugin-eslint 5.0.9CommonJS
- @babel/plugin-proposal-throw-expressions 8.0.1ESM-only