react

> TypeScript configuration for React libraries. Extends @jmlweb/tsconfig-base with JSX support, DOM types, and bundler-optimized module resolution.

✨ Features

🔒 Strict Type Checking: Inherits all strict TypeScript rules from base config
⚛️ JSX Support: Modern JSX transform (React 17+) with react-jsx
🌐 DOM Types: Includes DOM and DOM.Iterable libs for browser APIs
📦 Bundler Resolution: Optimized moduleResolution: "bundler" for modern build tools
🎯 Modern Modules: Uses ESNext modules for optimal bundling
🚀 Extensible: Extends base config, easy to customize

📦 Installation

pnpm add -D @jmlweb/tsconfig-react typescript @jmlweb/tsconfig-base

> 💡 Upgrading from a previous version? See the Migration Guide for breaking changes and upgrade instructions.

🚀 Quick Start

Create a tsconfig.json file in your project root:

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

💡 Examples

Basic Setup

{
  "extends": "@jmlweb/tsconfig-react",
  "include": ["src"],
  "exclude": ["node_modules", "dist"]
}

With Custom Output Directory

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

With Additional Compiler Options

{
  "extends": "@jmlweb/tsconfig-react",
  "compilerOptions": {
    "outDir": "./dist",
    "declaration": true,
    "declarationMap": true,
    "sourceMap": true
  },
  "include": ["src"],
  "exclude": ["node_modules", "dist"]
}

For React Library with Path Mapping

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

🤔 Why Use This?

> Philosophy: React development should leverage modern JSX transforms and bundler optimizations for the best developer experience and runtime performance.

This package provides a TypeScript configuration specifically optimized for React library and application development. It extends the strict base configuration while adding React-specific settings that work seamlessly with modern build tools and the latest React features.

Design Decisions

Modern JSX Transform (jsx: "react-jsx"): Uses the new JSX runtime from React 17+

Why: Eliminates the need to import React in every file, reduces bundle size, and improves build performance. The automatic JSX runtime is the recommended approach for all modern React projects
Trade-off: Requires React 17+ (which is several years old at this point). Older projects need to upgrade
When to override: Only if you’re stuck on React 16 or need the classic React.createElement transform for legacy compatibility

Bundler Module Resolution (moduleResolution: "bundler"): Optimized for modern build tools

Why: Modern bundlers like Vite, Webpack 5+, and esbuild benefit from bundler resolution, which enables better tree-shaking and handles modern module features. This matches how your build tool actually resolves modules
Trade-off: Not suitable for direct Node.js execution without a build step. But React projects always use bundlers anyway
When to override: Never for React libraries - this is the optimal choice. Use @jmlweb/tsconfig-node for Node.js projects instead

DOM Type Definitions (lib: ["ES2022", "DOM", "DOM.Iterable"]): Includes browser APIs

Why: React components interact with the DOM. Including DOM types prevents type errors when using window, document, event handlers, and other browser APIs that are fundamental to React development
Trade-off: Includes types you won’t use in server-side code. But React Server Components and SSR still need DOM types for shared components
When to override: For purely server-side React code (rare). But even Next.js server components often need DOM types for shared code

ESNext Modules (module: "ESNext"): Modern module syntax for optimal bundling

Why: Bundlers work best with ESNext modules. They can perform advanced optimizations like scope hoisting and dead code elimination. Your bundler transpiles to the target environment anyway
Trade-off: Can’t run the TypeScript output directly in Node.js without a bundler. But React projects always use bundlers
When to override: Never for React projects - let your bundler handle the final module format

📋 Configuration Details

What’s Included

This configuration extends @jmlweb/tsconfig-base and adds:

✅ JSX Support: jsx: "react-jsx" for modern React JSX transform
✅ DOM Types: Includes DOM and DOM.Iterable libs
✅ Bundler Resolution: moduleResolution: "bundler" for modern build tools
✅ ESNext Modules: module: "ESNext" for optimal bundling
✅ All Base Config: Inherits strict type checking and best practices

JSX Transform

Uses the modern react-jsx transform (React 17+), which means:

✅ No need to import React in every file
✅ Automatic JSX runtime handling
✅ Smaller bundle sizes
✅ Better performance

Example:

// No React import needed!
export function Button() {
  return <button>Click me</button>;
}

Module Resolution

Uses bundler resolution, which is optimized for:

✅ Vite
✅ Webpack 5+
✅ Rollup
✅ esbuild
✅ Other modern bundlers

This allows for better tree-shaking and modern module features.

🎯 When to Use

Use this configuration when you want:

✅ React library development
✅ React component libraries
✅ React applications with TypeScript
✅ Modern JSX transform support
✅ Strict type checking for React code
✅ DOM API type support

For non-React TypeScript projects, use @jmlweb/tsconfig-base instead.

For internal tooling projects, use @jmlweb/tsconfig-internal instead.

🔧 Extending the Configuration

You can extend or override the configuration for your specific needs:

{
  "extends": "@jmlweb/tsconfig-react",
  "compilerOptions": {
    "outDir": "./dist",
    "jsx": "react-jsxdev", // For development builds
    "paths": {
      "@/*": ["./src/*"]
    }
  },
  "include": ["src"],
  "exclude": ["node_modules", "dist"]
}

📝 Usage with Scripts

TypeScript compilation is typically handled by your build tool. For manual compilation:

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

Usage with Build Tools

Vite

import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';

export default defineConfig({
  plugins: [react()],
});

Webpack

import type { Configuration } from 'webpack';

const config: Configuration = {
  module: {
    rules: [
      {
        test: /\.tsx?$/,
        use: 'ts-loader',
      },
    ],
  },
};

📋 Requirements

Node.js >= 18.0.0
TypeScript >= 5.0.0
React >= 17.0.0 (for JSX runtime support)

📦 Peer Dependencies

This package requires the following peer dependencies:

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

📚 Examples

See real-world usage examples:

example-react-typescript-app - React TypeScript app example

Internal Packages

@jmlweb/tsconfig-base - Base TypeScript configuration (extended by this package)
@jmlweb/eslint-config-react - ESLint configuration for React libraries
@jmlweb/prettier-config-base - Prettier config for consistent formatting
@jmlweb/vite-config - Vite configuration for React projects

External Tools

TypeScript - Strongly typed programming language that builds on JavaScript
React - JavaScript library for building user interfaces
Vite - Build tool with first-class TypeScript support
@vitejs/plugin-react - Official React plugin for Vite

🔄 Migration Guide

Upgrading to a New Version

> Note: If no breaking changes were introduced in a version, it’s safe to upgrade without additional steps.

No breaking changes have been introduced yet. This package follows semantic versioning. When breaking changes are introduced, detailed migration instructions will be provided here.

For version history, see the Changelog.

Need Help? If you encounter issues during migration, please open an issue.

📜 Changelog

See CHANGELOG.md for version history and release notes.

📄 License

MIT