canirequire

canirequire › No JS entry point › @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. Markdown · JSON

No JS entry point No JavaScript entry point

@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.
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

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.

Runtimerequire("@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.0✗ failsError✗ failsError

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 * as recommended from "@tsconfig/recommended";

CommonJS (require)

Not applicable.

Module format by version

Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (14 versions; the newest 14 shown).

VersionsFormatFirst published
1.0.0 – 1.0.13No JS entry pointAug 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

Other no js entry point packages

Similar popularity