npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@jmlweb/tsconfig-node

v2.0.1

Published

TypeScript configuration for Node.js and CLI projects. Extends @jmlweb/tsconfig-base with Node.js-specific settings excluding DOM types.

Readme

@jmlweb/tsconfig-node

npm version License: MIT Node.js TypeScript

TypeScript configuration for Node.js and CLI projects. Extends @jmlweb/tsconfig-base without DOM types.

✨ Features

  • 🔒 Strict Mode: inherits every strict flag from the base config
  • 🟢 Node.js Focused: lib: ["ES2022"], no DOM types
  • 🚀 NodeNext Modules: Node.js ESM/CJS resolution, inherited from base
  • 🎯 Flexible: no file patterns imposed

📦 Installation

npm install --save-dev @jmlweb/tsconfig-node @jmlweb/tsconfig-base typescript

🚀 Quick Start

{
  "extends": "@jmlweb/tsconfig-node",
  "compilerOptions": {
    "outDir": "./dist",
    "rootDir": "./src"
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules", "dist"]
}

💡 Examples

CLI tool

{
  "extends": "@jmlweb/tsconfig-node",
  "compilerOptions": {
    "outDir": "./dist",
    "rootDir": "./src"
  },
  "include": ["src/**/*"]
}

Typecheck only (with a bundler or tsx)

{
  "extends": "@jmlweb/tsconfig-node",
  "compilerOptions": {
    "noEmit": true,
    "module": "ESNext",
    "moduleResolution": "bundler"
  },
  "include": ["src/**/*"]
}

📋 Configuration Details

Extends @jmlweb/tsconfig-base and adds:

| Option | Value | Description | | ------ | ------------ | ------------------------------ | | lib | ["ES2022"] | ES2022 APIs only, no DOM types |

All other options (strict, target: ES2022, module/moduleResolution: NodeNext, verbatimModuleSyntax, …) come from the base config. With NodeNext, relative imports need .js extensions.

🎯 When to Use

  • ✅ Node.js applications, APIs and services
  • ✅ CLI tools and scripts
  • ✅ Server-side libraries

Browser or React code: use @jmlweb/tsconfig-react. Need DOM types in Node.js (for example fetch typings): add "lib": ["ES2022", "DOM"].

🔧 Extending the Configuration

{
  "extends": "@jmlweb/tsconfig-node",
  "compilerOptions": {
    "lib": ["ES2023"],
    "types": ["node"]
  }
}

📝 Usage with Scripts

{
  "scripts": {
    "build": "tsc",
    "typecheck": "tsc --noEmit"
  }
}
npm run typecheck

📋 Requirements

  • Node.js >= 22.12.0
  • TypeScript >= 5.0.0

📦 Peer Dependencies

  • @jmlweb/tsconfig-base (^2.0.0)
  • typescript (>=5.0.0)

🔗 Related Packages

🔄 Migration Guide

1.x → 2.0.0

Breaking: Node.js >=22.12.0 is now required (Node.js 18 and 20 are end-of-life).

  1. Upgrade Node.js to 22.12.0 or later.
  2. Update the package: npm install --save-dev @jmlweb/tsconfig-node@^2.0.0.

The compilerOptions are unchanged. See the Changelog.

📄 License

MIT