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

nl.js

v0.1.1

Published

Create a basic project json file, and then launch it with one command.

Downloads

3

Readme

#nl.js A small node tool for launching projects in one command.

##Why? As a web developer, I've noticed a considerable amount of time being spent switching between projects. Because the web is such a rich place now, each time I switch projects, I have to open any number of the following things:

  • Photoshop / Gimp / Inkscape / The artwork in general
  • An editor / IDE
  • A terminal window that's in the correct path
  • Sass, Grunt and other "pre-processing" things
  • Git / issue pages

I wrote nl.js to streamline this process. Each project I work on gets a dedicated nl.json file stored in ~/projects. Now each time I open a project to begin work, I simply open a terminal, cd ~/projects/project-name && nljs.

###It's messy It's a personal tool, developed exactly how I've required it, sorry.

###Using nljs

This has only been tested on a Debian (Ubuntu) environment.

cd /tmp
git clone https://github.com/isdampe/nl.js.git nljs-master
cd nljs-master
sudo sh install.sh
cd /path/to/project
nljs init
vi nl.json

Make your changes and save it, and then finally to execute all of apps:

nljs