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

create-typescript-react-library

v1.0.0-alpha.2

Published

🧰 Tool for building low-maintenance, flexible TypeScript libraries.

Downloads

9

Readme

create-typescript-react-library

npm version test coverage GitHub Workflow Status

This starter enables simple creation of libraries using TypeScript.

Features

  • [x] rollup for smallest bundles
  • [x] tests with jest (+coverage)
  • [x] generates type declarations
  • [x] esm, cjs and umd (script tag) exports
  • [x] admin (code of conduct, contributing instructions)
  • [x] interactive setup script
  • [x] automated semantic releases
  • [x] automated api docs generation
  • [x] add react with a single command
  • [x] context-dependent start script (tdd jest, plus storybook for react)

Requirements

  • curl
  • git
  • node
  • yarn

Setup

Step 1. Local setup

yarn create typescript-react-library <yourdir>
cd <yourdir>

# install dependencies
yarn
# start setup
yarn ctrl setup
# re-init history
rm -rf .git
git init
# if adding react
yarn ctrl add-react
# create repo and push changes
git add -A
git commit -m 'Initial commit' --no-verify
git remote add origin https://github.com/<user>/<repo>.git
git push -u origin main

Step 2. Github setup

  1. Create an NPM token: https://docs.npmjs.com/creating-and-viewing-authentication-tokens
  2. Create a Github repo of the same name that you selected in the setup script
  3. Add the NPM token to your repository's secrets: your-repo > Settings > Secrets > New Secret NPM_TOKEN=<your token from Step 1>

Step 3. Go!

yarn start


I'm not creating a React library

yarn remove react react-dom

Also, my library is for node, not the browser

Remove the browser key in package.json.

Pointers

  • If you want to bundle a package you're importing, stick it in dependencies. If you'd like the user of your library to install it as a peer dependency, install it as a peer dependency
    • Peer dependencies in web (umd) builds are imported by getting it from the window object. Web versions of different dependencies often use different global names (window.$ might be used in import ... from "jquery"). For web builds to work, you'll have to add the correct global name to the knownDependencyNames map in rollup.config.js