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 🙏

© 2024 – Pkg Stats / Ryan Hefner

fastify-tsconfig

v2.0.0

Published

Shared TypeScript configuration

Downloads

134,242

Readme

tsconfig

Shared TypeScript configuration for fastify projects

Install

$ npm install --save-dev fastify-tsconfig

Usage

Create your own tsconfig.json in the projects' root folder and extend it from fastify-tsconfig, overriding or adding the desired settings. By default, no outDir is set (because of this issue), so be sure to add one.

Configuration module and moduleResolution

This configuration sets "module" and "moduleResolution" to NodeNext. This means that TypeScript will read the nearest package.json file in the scope and search for the "type" field or the absence of it.

If type is not set or is "type": "commonjs" the emitted code will be CommonJS, with .js extension. Moreover, tsc will complain if ESM-only properties/features are used in source files. If you want to emit .mjs files, use the .mts extension. On the other hand, if "type": "module" is set, the sources will be compiled to the ESM with the .js extension. In this case, if you want to emit .cjs files, use the .cts extension for the source file.

The "following the Node.js rules" goes also for the package.json exports field. If type is set, regardless of the value, TypeScript will check the exports field to know where the compiled code and the types are located. If the type field is not set, it will check for the main and types fields.

CommonJS example

package.json

{
  "name": "my-package",
  "type": "commonjs",
  "main": "dist/index.js", // this is for older Node.js versions
  "types": "dist/index.d.ts", // this is optional and can be omitted
  "exports": {
    "import": "./dist/index.js",
    "require": "./dist/index.js",
    "types": "./dist/index.d.ts" // this is optional and can be omitted
 }
}

tsconfig.json

{
 "extends": "fastify-tsconfig",
 "compilerOptions": {
    "outDir": "dist",
    "sourceMap": true
  },
  "include": [
    "src/**/*.ts"
  ]
}

ESM example

package.json

{
  "name": "my-package",
  "type": "module",
  "main": "dist/index.js", // this is for older Node.js versions
  "types": "dist/index.d.ts", // this is optional and can be omitted
  "exports": {
    "import": "./dist/index.js",
    "require": "./dist/index.js",
    "types": "./dist/index.d.ts" // this is optional and can be omitted
 }
}

tsconfig.json

{
 "extends": "fastify-tsconfig",
 "compilerOptions": {
    "outDir": "dist",
    "sourceMap": true
  },
  "include": [
    "src/**/*.ts"
  ]
}

Extending this configuration

Depending on the type of the project, you should add the following settings.

Application

tsconfig.json

{
 "extends": "fastify-tsconfig",
 "compilerOptions": {
    "outDir": "dist",
    "sourceMap": true
 },
 "include": [
    "src/**/*.ts"
 ]
}

NPM Package

tsconfig.json

{
 "extends": "fastify-tsconfig",
 "compilerOptions": {
    "outDir": "dist",
    "declaration": true
 },
 "include": [
    "src/**/*.ts"
 ]
}

Monorepo Package

tsconfig.json

{
 "extends": "fastify-tsconfig",
 "compilerOptions": {
    "outDir": "dist",
    "declarationMap": true,
    "composite": true
 },
 "include": [
    "src/**/*.ts"
 ]
}

Check the other settings here

Configuration target

The configuration targets ES2022, which is supported in Node.js 16 and later. Only one feature still needs to be implemented: RegExp Match Indices shows up in flags. However, using ES2022 as a target makes widely used features not being compiled. To target an older version, override the target property.

License

Licensed under MIT.


Inspired by: sindresorhus/tsconfig