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

autobuild

v0.0.2

Published

continous integration on the devloper pc

Downloads

8

Readme

Autobuild

Autbuild is continous integration on the developer PC.

The main idea behind autobuild is, instead of hitting build, check and deploy in your IDE or command line, autobuild will to that for you. You change a file everything gets built, checked and deployed. What build, check and deploy means is up to you, you specify it in a JSON file.

Examples

The following example shows the autobuild definition for a make file oriented project.

autobuild.json:

{
    "name": "My Project",
    "sources": {
        "directories": [
            "./include",
            "./src",
            "./src/extra",
        ],
        "patterns": [".cpp", ".h"]
    },
    "build": {            
        "cwd": "./build",
        "command": "make"
    },
    "check": {
        "cwd": "./build",
        "command": "make check"
    },
    "deploy": {
        "cwd": "./build",
        "command": "make install"
    }
}

The following example shows the autobuild definition for a Visual C++ 6 project.

autobuild.json:

{
    "name": "Custom Requirements Assesment Program",
    "sources": {
        "directories": [
            "y:\\CRAP_SRC\\_inc",
            "y:\\CRAP_SRC\\crap",
            "y:\\CRAP_SRC\\utils",
        ],
        "patterns": [".cpp", ".cc", ".h", ".hpp"],
    },
    "build": {
        "cwd": "y:\\CRAP_SRC\\_equ",
        "command": "msdev.exe crap.dsw /MAKE \\"ALL - RELEASE\\""
    },
    "deploy": {
        "source": "y:\\CRAP_DO\\win23\\release",
        "target": "C:\\Program Files\\Crap",
        "files": [
            "crap.exe",
            "crap.pdb",
            "utils.dll",
            "utils.pdb"
        ]
    }
}

Installation

Autobuild uses node, you need a proper installation of node (including npm).

The easiest way to install it is with npm:

npm install -g autobuild

Usage

You can either invoke it as a command line utility

autobuild autobuild.json

or with a user interface

autobuild index.js --gui autobuild.json

Known Issues

  • On windows not the user interface may not work because of some odd appjs shenanigans. When you get the error "Error: CEF location not found" that is it.