# Is @tsconfig/recommended ESM-only? Can you require() it?

> @tsconfig/recommended@1.0.13 has no importable main entry. No JavaScript entry point.

A base TSConfig for working with Recommended.

Last verified Sep 9, 2026 against @tsconfig/recommended@1.0.13.

@tsconfig/recommended does not expose a JavaScript entry point in package.json. It is likely a CLI, a stylesheet, a type-definition package, or an asset bundle, so require() and import are not the way to use it.

## What to do

1. Do not require() or import @tsconfig/recommended: it has no JavaScript entry point. Use it as a CLI (npx @tsconfig/recommended), a stylesheet, an asset, or a type-definition package as its README describes.
2. TypeScript: no types are available for @tsconfig/recommended; declare the module yourself if you need them.

## Facts

- Latest: 1.0.13 (Nov 13, 2025)
- Module format: No JS entry point
- Last CommonJS version: n/a
- TypeScript types: none
- Node engines: not declared
- Weekly downloads: 330K
- License: MIT

## Runtime test results for @tsconfig/recommended@1.0.13

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 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Node.js 20 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Node.js 22 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Node.js 24 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Node.js 26 | fails (MODULE_NOT_FOUND) | fails (ERR_MODULE_NOT_FOUND) |
| Bun 1.4.0 | fails (Error) | fails (Error) |

## How to import @tsconfig/recommended

ES modules:

```js
import * as recommended from "@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 | No JS entry point | Aug 6, 2020 |

## Frequently asked

**Is @tsconfig/recommended ESM-only?**

@tsconfig/recommended@1.0.13 has no importable main entry. @tsconfig/recommended does not expose a JavaScript entry point in package.json. It is likely a CLI, a stylesheet, a type-definition package, or an asset bundle, so require() and import are not the way to use it.

**Does @tsconfig/recommended work in Bun?**

Importing @tsconfig/recommended failed in Bun 1.4.0 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

- [@tsconfig/recommended on npm](https://www.npmjs.com/package/@tsconfig/recommended)
- [Source repository](https://github.com/tsconfig/bases)
- [HTML version](https://canirequire.com/package/@tsconfig/recommended/)
- [JSON version](https://canirequire.com/package/@tsconfig/recommended.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.