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

krunch

v0.1.2

Published

A simple build and watch tool for javascript, html and less/css.

Downloads

9

Readme

Krunch

NEEDS REWRITE

Krunch is a NodeJS module entended to help a developer quickly organize a static codebase.
Krunch will concat, minify, and uglify LESS, JS and HTML files upon file change while you build whatever it is that you're developing.
Krunch is not suited for a production environment and works best for static websites, prototyping or full Javascript based applications.
Krunch is built for speed and watches only files that you specify in your configuration.
As of now Krunch will not watch entire directories or LESS import paths.

Installation

npm install krunch -g

Configuration

Krunch requires a json configuration. Set defaults and overwrite them where necessary. Our program defaults are in the example below.
(Javascript syle comments are supported in your json config)

Example JSON Configuration

{
    "default": {
        "html": {
            "path": ""
        },
        "js": {
            "path": "",
            "minify": true,
            "uglify": true,
            "beautify" false
        },
        "less": {
            "path": "",
            "import_paths": [".", "./less", "./css"],
            "minify": true
        }
    },
    "html": [
        {
            "files": [
                "html/layout.html",
                "html/about.html",
                "html/sitemap.html",
                "html/services.html",
                "html/tos.html",
                "html/contact.html"
            ],
            "output": "html/site.html"
        }
    ],
    "js": [
        {
            "files": [
                "js/shared/jquery.js",
                "js/shared/jhomie.js",
                "js/jscript.js"
            ],
            "uglify": false,
            "output": "/js/site.js"
        }
    ],
    "less": [
        {
            "path": "somewhere_else",
            "files": [
                "less/reset.less",
                "less/site.less"
            ],
            "output": "css/site.css"
        },
        {
            "files": [
                "less/admin.less"
            ],
            "output": "css/admin.css"
        }
    ]
}

Now you can include one css/js file in your html vs including all of them, organize files, minify, uglify, and limit your page requests.

Options and Defaults

Krunch will re-watch your files upon modification to your configuration unless it has been invoked dynmaically through node with no config file.

Files and output locations are required for each krunch job.

Paths found in the default are only prepended to each array of input files. Please specify a direct output file with the full path from root of your project.

If your LESS files use import functionality you will need to specify import paths if your imported less files can not be found by default in the root, /css or /less directories.

Krunch can be called through node.

var krunch = require('krunch');
krunch(your_json_configuration_or_path_to_config_file);

Run Krunch

cd root_of_project
krunch path_to_config_file