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

shebang-it

v0.0.6

Published

shebang-it

Downloads

18

Readme

shebang-it

What is it?

Maybe I'm missing something, but it seems like the offerings of parcel-bundler, and webpack are missing a crucial lib to do with the usability of bundled command line utilites:

You need to be able to actually run them.

So, I wrote a tiny util to take a bundled js file, slap a shebang on top, move it into a bin folder, and give it executable perms. I've been passing this around a few of my cli util projects for a while, and figured it was high time to make it official. So now it is!

How to use it?

shebang-it takes a single argument: the folder path to the file you'd like made executable, and it defaults to dist

it can also take the following optional properties if you want to get creative with creating tons of different bin files:

| Arg | Longform | Description | Example | | :---------------: | :---------------: | :--------------- | ---------------: | | -i | --input-filename | custom filename for the assumed dist util | shebang-it -i windex.js | | -o | --output-filename | custom filename for the output bin util | shebang-it -o shebang-it.js |

As part of my build process with husky and lint-staged, I like generating the files automatically. That way, in a precommit, the bin file will always be up to date, and when using the np library to push updates to npm there won't be anything to blame for the right code not landing.

TODO:

THE ISSUE 0. PATCH OUR DEFAULT BACK OUT WHEN THE ISSUE IS RESOLVED signale issue np issue ava issue

It seems like execa (another sindresorhus package) hijacks the output stream. This meant that any cli package using shebang-it would explode when trying to use np to update itself. That's super annoying. It seems like a lower priority thing, so in the meantime, I've added a small bit of code to default the stdio stream if it's not present to a nooplike thing. I'm unhappy with this, and want it gone ASAP.

  1. add it to project-status
  2. generate a couple badges
  3. add it to travis-ci
  4. report coverage
  5. report test percentage
  6. report code quality
  7. add option for silent execution
  8. add a ricky-martin themed svg logo