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

ez-publish

v1.0.0-alpha.16

Published

Command line tool for publishing js libraries

Downloads

6

Readme

ez-publish

Opinionated command line tool for publishing javascript libraries

ez-publish

Publishing javascript libraries to bower can be very difficult. Bower expects that distribution files (babelified, uglified, webpackyfied, blubberyfied, ..) are present in the tagged commits. At least our users expect that. Having distribution files in the commit history sucks. This is why some projects (e.g. quill) don't even publish distribution files in the tagged commits. This sucks for the user (not everyone wants to use 99 transpilation tools). Other projects (e.g. ace) have a dedicated project for publishing distribution files. This sucks for the developer. I think this approach sucks less.

What it does

We use a nifty trick to tag distribution files without fucking up our commit history:

  • git checkout --detach We detach the head. This means we no longer track any branch
  • git add -f ./dist project-name* We force to add all distribution files
  • git commit -am 'Publish vX.Y.Z -- with dist files' Commit dist files
  • git tag vX.Y.Z Tag release with dist files
  • git push origin vX.Y.Z Push tag
  • git checkout master Revert to tracking master branch (dist files are no longer tracked / in the git history)

What it also does

  • Adds that release message to ./CHANGELOG.md, and to the tag description
  • OPTIONAL: You can work on ./.releaseMessage before you publish using ez-publish

Checklist

This tool is for you if.. (all of the following must be true)

  • [x] You have a package.json.
  • [x] All files you want to distribute are in ./dist or match ./PROJECTNAME*.Where PROJECTNAME is given by require(package.json).name
  • [x] You understand what it does
  • [x] You work in a unix-ish environment (Linux | Mac (untested) | Windows with Cygwin (untested))

Tutorial

$ npm i -g ez-publish
$ publish

It is a good idea to write a prepublish script in your package.json (overwrites default behavior of npm publish)

..
  "scripts": {
    ..
    "prepublish": "npm run dist && npm run lint",
    "postpublish": "publish"
  }

Then you can just run npm publish, and automatically create tags etc..