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

algob

v0.0.5

Published

This package provides the main entry point into the application.

Downloads

4

Readme

Builder

This package provides the main entry point into the application.

Usage

It can be included as a library by importing internal/lib/lib.ts or be run from command line.

Command line usage

Before running tasks it will check for presence of algob.config.js. If it's not present the project will be generated in the current directory. After that other commands will be possible to execute.

Help algob help

View version algob --version

Launch a node project console algob console

Development-mode usage

Copied files won't overwrite already existing ones so running yarn algob should result in an error if any files clash. It's best to use a different directory to initialize test projects.

Also, it my be helpful to link the binary:

yarn link

Contributing

When working on algob, we use CLI directly from the build directory using the following command:

yarn run algob:dev

It will create a project-dev directory as a copy of the template project (sample-project). In that directory you should update the config.algob.js. The algob:dev command will run all algob in that directory.