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

lakeside

v1.0.0

Published

CLI command runner

Downloads

4

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

pixeldesupixeldesu

Keywords

clicommandsrunnernode

Readme

lakeside

A dependency-free Node.js command/task runner!

Prerequisites

  • Node.js

Installation

Locally inside a project:

$ npm i lakeside

Globally, best for lakeside CLI usage:

$ npm i -g lakeside

Usage

Running lakeside on your command line will show you the CLI and flag reference, as well as all currently available commands, if configured!

Note: lakeside will throw errors if it can't find a configuration, so please make sure to configure it properly before attempting to use it!

Documentation

To get lakeside up and running for your projects, follow the documentation:

Motivation

I envisioned and built this tool because of a problem at in2code GmbH, where we switched away from Gulp to npm scripts. With a lot of different things required for projects, we quickly amassed 46 scripts, which got confusing especially for non-frontend people that quickly need to build something.

While lakeside takes a bit more effort to configure/write than regular npm scripts, it is not limited to the CLI, so it can easily leverage all kinds of Node packages and file system features.

With the global configuration it offers, there also is deduplication with configuration values that often have to be repeated many times in npm scripts.

It was also made to be lightweight, so it uses no dependencies at all and implements everything, from CLI argument parsing to configuration handling itself.

Contributing

There are many ways to contribute and all of them are welcome!

License

lakeside is licensed under the MIT License