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

ztate

v2.0.1

Published

A simple state machine library for React

Downloads

3

Readme

Create TypeScript Package

A template project for creating TypeScript packages.

Configuration

  1. Replace the package name, description, author, license, etc. in the package.json with your package's details

  2. Update this README.md file to contain your package's documentation

  3. Update the release.yml workflow to check for your username when publishing (this is used to prevent the workflow from running in forks):

    if: startsWith(github.repository, '{your-username}/')
  4. Configure GITHUB_TOKEN to have the permissions to create Pull Requests:

    1. Go to https://github.com/{owner}/{repo}/settings/actions
    2. Check "Allow GitHub Actions to create and approve pull requests" under "Workflow permissions"
  5. Add NPM_TOKEN to your Repository secrets:

    1. Go to NPM's Access Tokens page
    2. Click "Generate New Token" -> "Classic Token" and follow the instructions (make sure to choose "Automation" for the token type)
    3. Go to https://github.com/{owner}/{repo}/settings/secrets/actions, and add the generated token as a secret named NPM_TOKEN

Structure

  • src/ - TypeScript source files.
  • **/__tests__/ - Test files.
  • dist/ - Compiled JavaScript files.

Tools

This template uses tsup for transpiling & bundling, Vitest for testing, ESlint & TypeScript ESlint (with the strictest configuration) for linting, Prettier for formatting, and Changesets for versioning & publishing.

Development Flow

  1. Add your code & tests to the src/ directory

  2. Use npm run test to run the tests

  3. Use npm run lint to lint the code

  4. Use npm run format to format the code

  5. Use npm run build to build the package

  6. Run npx changeset each time you want to add a commit to the changelog (see Using Changesets for more info)

  7. Commit & push your changes

  8. The CI will automatically open a PR with the changes, or add the changes to an existing PR

  9. Review & merge the PR when you're ready to publish the package