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

@r-t-p/particles

v0.0.3

Published

This is a simple typescript template repo for getting started. Start coding index.ts. Tooling uses:

Downloads

1

Readme

clean-typescript

This is a simple typescript template repo for getting started. Start coding index.ts. Tooling uses:

  • tsc for building
  • jest for testing
  • npm for versioning
  • .github/workflows (i.e github actions) for automation
  • releasing on github will publish to npm

If you want to release to npm you can release with the button in github and the github actions will ship it to npm.

If you are using this in your own project and want to publish to NPM you will need to save a token

To Do with a new repo

  • [ ] Update the package.json with the correct repo and name
  • [ ] Publish to npm for the first time. Doing it locally with npm publish --access=public is probably easiest
  • [ ] Clear template info for readme and update with better info

Versioning

These commands should be run from the master branch when ready to bump a version. Bumping a version will commit the bump and push it up as long as pushing tags up for release.

  • npm run bump - Bumps current version i.e. 1.2.4 would bump to 1.2.5
  • npm run bump-minor - Bumps Minor version i.e. 1.2.4 would bump to 1.3.0
  • npm run bump-major - Bumps current version i.e. 1.2.4 would bump to 2.0.0

In your repo, delete above this and carry on with your new repo ^^^

Getting Started

Contributing

Pull requests are welcome, if you add bloat they will be rejected. Keep things simple.

Running locally

npm run test # Runs the test runner
npm run build # Builds using `tsc` from configs in the `tsconfig.json`
npm run dev # Runs build and watches for changes

Under the hood

  • tsc for building js sent to /dist/
  • jest for testing all .test.ts or .spec.ts files and files in __test__
  • npm for versioning
  • .github/workflows (i.e github actions) for automation
    • main.yml runs tests and build on all branches
    • publish.yml ships code to npm when a release is published