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

monofile

v0.1.0

Published

export MONOFILE="$0"; cat "$0" | awk '/\<a name\=\"2\.1\.\"\>/{y=1;next}y' | tail -n+3 | bash -euo pipefail -- /dev/stdin "$@"; exit 0 -->

Downloads

4

Readme

#!/bin/bash -euo pipefail #<!-- export MONOFILE="$0"; cat "$0" | awk '/<a name="2.1.">/{y=1;next}y' | tail -n+3 | bash -euo pipefail -- /dev/stdin "$@"; exit 0 -->

Monofile

What would be the perfect way to reduce all of your problems down to one single problem? Putting everything in the same file 🙌

Table of contents

  1. Monofile documentation
  2. Monofile implementation
  3. Your code 😎

1. Monofile documentation

Monofile couldn't be easier to use, everything you need is in this file. For convenience we have published this file to npm, but you could just as easy download this file and put it in your path.

1.1. Installation

npm install --global monofile

1.2. Usage

To initialise a new monofile, run the following command to create a new README.md file in the current directory.

monofile init

To run your command, use the builtin run command.

./README.md run

2. Monofile implementation

2.1. Bootstrapping

if [ "$#" -ne 1 ]; then
  >&2 echo "Please give monofile exactly one argument"
  exit 1
fi

if [ "$1" == "init" ]; then
  if [ -e README.md ]; then
    >&2 echo "Monofile allready initialised"
    exit 1
  fi

  cat "$MONOFILE" > README.md
  chmod +x README.md
fi

if [ "$1" == "run" ]; then
  BOOTSTRAP_LANGUAGE="$(cat "$MONOFILE" | awk '/\<a name\=\"3\.1\.\"\>/{y=1;next}y' | tail -n+2 | head -n 1)"

  if [ "$BOOTSTRAP_LANGUAGE" == '```javascript' ]; then
    cat "$MONOFILE" | awk '/\<a name\=\"3\.1\.\"\>/{y=1;next}y' | tail -n+3 | awk '/```/{exit};1' | node
  else
    >&2 echo "Unsupported language: \"$BOOTSTRAP_LANGUAGE\""
    >&2 echo "Please file an issue at https://github.com/LinusU/monofile/issues"
    exit 1
  fi
fi

exit 0

3. Your code 😎

3.1. Bootstrapping

console.log('🔥  This is the place where your code should live 🔥')