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

@kamatte-me/npm-sandbox

v0.7.5

Published

My sandbox project

Downloads

1

Readme

@kamatte-me/npm-sandbox

My NPM sandbox project.

Build ESM / CJS package with TypeScript.

Tools

Getting Started 🚀

  1. Create a new GitHub repository
  2. Download this repository
  3. Modify the Release Workflow in .github/workflows/release.yml
    - branches:
    -   - main
    + branches-ignore:
    +   - '**'
  4. Modify the Changesets config in .changeset/config.json
    - { "repo": "kamatte-me/npm-sandbox" }
    + { "repo": "<your-org>/<your-repo>" }
  5. Update the following package information in package.json
    • name
    • version: 0.0.0
    • description
    • keywords
    • homepage
    • repository
    • license
    • author
  6. Update README.md
  7. Update LICENSE
  8. Push to GitHub
    git init
    git add --all
    git commit -m "first commit"
    git branch -M main
    git remote add origin [email protected]:<user>/<repo>.git
    git push -u origin main
  9. Configure GitHub repository Settings
    • Actions > General > Workflow permissions
      • Enable Allow GitHub Actions to create and approve pull requests
    • Secrets and variables > Actions > New repository secret
      • NPM_TOKEN: Your NPM Granular Access Token
  10. Install the following GitHub Apps
  11. DEVELOP YOUR LIBRARY
  12. First Release 🎉
    1. Set the version in package.json
    2. Revert the .github/workflows/release.yml changes

After First Release

For each Pull Request

  1. Before merging a pull request, either run pnpm changeset or follow the comments from changeset-bot on the pull request, decide on the release type and write the release notes.
  2. Confirm that the changeset-bot has commented 🦋 Changeset detected on the pull request before merging.
  3. Merge the pull request.

For each release

Merge the pull request titled Version Packages.