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

to-do-list-checker

v4.0.0

Published

Checks a list of to do items to determine if the project is ready for release.

Downloads

89

Readme

To do list checker

Checks a list of to do items to determine if the project is ready for release. Sounds weird? Read some details of what I mean by that and how this changed the way I develop.

Development

The following describes how to (help) develop this code.

Setup and run

Project requires NodeJS to be installed.

  • cd <here>
  • (if you want a reproducable env using nix) run nix-shell
  • npm i to install
  • npm test to run all the tests
  • develop ...

Install/setup, via nix

The project can be built and run locally using nix, to reproduce the environment.

  1. Make sure to have nix installed (see nixos.org/nix) and then
  2. cd <project-dir>
  3. run nix-shell and you should have the environment up and running
  4. install all node modules using npm install
  5. prove that it works, npm test
  6. now you have a shell with a deterministic environment (incl. node version)

Releasing

You want to know if you are ready to release a new version. Run npm run releasable --silent, this starts a script that checks the CHANGELOG.md, which is your to-do list! What, to-do list? Yes. See below how and why?

To release a new version run npm run release (not npm version!), this will include the checks described and do the release and versioning (read more below). To make it public on npm run npm publish, if you have permissions on this project the new version might go live.

Recommended Development Process

After all changes, before releasing, we always want to get some kind of list of what we did, a changelog. Creating a changelog after building the next cool feature is quite tedious, even scripts that run through commit messages (even when they have a certain format), is just not to the point, because it starts from the code. Not from the user! Let's turn it around.

Just like in TDD, where I write first a test for what we are planning to code, I started to go one level up and describe the user's feature first. I start writing things in the changelog, prefixed with the github style checkboxes [ ] (for unchecked) and once I finished the thing I change it to [x].

In the beginning this felt quite strange. But once I got used to it, the plan for the next version (see Versioning below) had always been in the CHANGELOG.md and I "just" had to work it off. Technical things, like refactoring, etc. went into the commits, but never into the changelog, they naturally don't belong there anyways. Meanwhile, the changelog lines even become my commit messages, once I really start or finish building the feature. I tick the feature/task off in the changelog and one can even see in the commits when a certain feature was done.

Here is the process in bullet points:

  1. Write out all planned features, to-dos in the CHANGELOG.md
  2. Make each one line, and prefix this line with [ ]
  3. The headline of this section, is the next (major) version number, e.g. # v1.0.0
  4. (Every item, you plan for some future version put it either above the headline of the next version or in your issue tracker)
  5. Work off one feature/to-do at a time
  6. Tick off the line in the changelog and commit it
  7. When all items are done release, using npm run release

Tip: If you write less features/to-dos per version, you can release more often, get faster feedback and can stay focused. Don't overestimate your speed, add less features, and you will ship happier.

Versioning

Semantic versioning looks nice on paper, but every change is essentially an external API change, if it is for speed, compatibility or any other change that might be "invisible" (to tests). The browsers and many software vendors have gone towards major-only versioning. Therefore I simplified the versioning process too, just use major versions and provide a proper changelog, that a user can understand.