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

strictts

v0.1.23

Published

Stricter tsc/tslint config defaults to bring safer developer experience

Downloads

28

Readme

TypeScript config compilerOptions reasonable defaults with type safety focus.

Read annotated version to get more details about each changed default. Configs are grouped into sections as they are in official compilerOptions reference.

Start new TypeScript project with tsconfig.json:

{
    "extends": "strictts",
    "compilerOptions": {
        ...
    },
    ...
}

and define project-specific options (take tsconfig-project.json as default). tsconfig-project.json is a recommended place to go if you start pure TS project aimed ES2019 runtimes.

I'm working on the React.js UI framework using TypeScript compiler configured with these defaults. The project contains more than 20k lines of code and thrown zero runtime exceptions (from ES2019-compliant environments) for more than six months in production.

I do not include lib.dom to default compilation to ensure global namespace be pure ES2019 prelude.

I do:

import env from "env"
env.console.log(env.document.body)

where env module is environment-specific module which is env.d.ts from TS distro if I run project in a web browser, or jsdom bindings if I run project in Node.js test env, and so on. Explicit definition of environment bindings (or declarations) helps me to deliver solid reliable code which runs in defferent environments without runtime exceptions.