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

@toml.dev/scripts

v4.2.2

Published

A bunch of scripts for development

Downloads

7

Readme

@toml.dev/scripts

One place for all the config that I usually have to pull together each time I start I new project. Nothing too fancy. Nothing too special. A little time saved — that's all!

It does do 2 things:

  1. Provides a set of npm run scripts that can be automatically installed into your package.json file scripts section.
  2. Provides a set of configuration files for the associated tooling.

See Tooling for more information.

Installation

npm install --save-dev @toml.dev/scripts

Usage

To install the npm run scripts into your package.json and copy the configuration files to the root of your project, in the same directory as your package.json, run:

npx tl-install

This command is non-destructive and idempotent. It will not overwrite run scripts that have the same name, nor will it copy over existing configuration files with the same names.

Tooling

Babel

Configured with React, Styled Components, and as the Typescript parser. It will also copy a script for including babel register in various run scripts into ./scripts/babel.js.

Editor Config

Basic support for most files with a special case for Makefiles.

Eslint

Configured to support Typescript, react, and with the default recommended rules. Some some very minimal tweaks to better support my personal coding style.

Jest

Typescript support with babel-jest. Supports tests inside folders with the name __test__ and that have the extension .test.ts. It also collects coverage from any files (that aren't these test files) inside the ./src directory of the project.

Prettier

The only change to the defaults is "proseWrap": "always" so I can format markdown files a little nicer and avoid soft wrapping in vscode which is a pain to edit with with navigating vertically.

Stylelint

Very basic config, just to support styled-components.

Typescript

Typical strict Typescript configuration for use with Babel as the actual parser. Not intended for actually outputting JS from the TS files.