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

@codecompose/typescript-config

v1.2.0

Published

Opinionated reusable TypeScript configurations

Downloads

162

Readme

typescript-config

Opinionated reusable Typescript configurations, assuming:

  • A monorepo setup (*)
  • Transpile using a bundler
  • Strict rules
  • Use of src and dist directories
  • Use of ~/ as path alias for src

(*) Use the single-*.json variants if you do not use a monorepo setup.

Warning

At the time of writing, not all tooling correctly interprets the extended config.

  • Next.js will require you to explicitly defined "includes". Give it "src" and it will inject its types on startup.
  • TSUP will not understand the tsconfig if you ask it to generate type definitions. I use tsc to generate the types, as demonstrated in mono-ts.

Install

pnpm i @codecompose/typescript-config -D

...or the equivalent for your package manager.

Usage

{
  "extends": "@codecompose/typescript-config/single-react-library.json"
}

Available Configurations

  • base
  • library
  • react-library
  • service
  • nextjs
  • single-library
  • single-react-library

For something else, like a CLI or E2E app you can probably just use the base.json configuration.

Assumptions and Recommendations

Source maps are not enabled, because we assume that your bundler will handle that.

All configurations have incremental set to true. In my experience, it can happen that builds get stuck in limbo and you need to delete the tsbuildinfo file to get things going again. For this reason I recommend adding the following script to your manifest based on del-cli:

"clean": "del dist tsconfig.tsbuildinfo"