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

crunchicorn

v0.0.3

Published

Batteries included CSS/JS transpiler/linker/compressor

Downloads

14

Readme

crunchicorn: Simplifying the web toolchain

The JavaScript ecosystem is complex and continually evolving. This is an attempt to simplify it. Goals of this project:

  • Provide an out-of-the-box toolchain for JS/CSS projects
  • Highly opinionated sensible defaults
  • Embrace modern standards
  • Command line tool (plays well with other tools, including shell scripts, make, npm run, etc)
  • NO CONFIG FILES
  • 'Batteries included' toolchain: ES2015 (and more) transpiling, enforce coding standards, ES import module packaging, shrinking, testing, CSS pre-processing
  • Designed for browser apps - you don't need to know NodeJS
  • Agnostic about client side frameworks (use React, Angular, jQuery, Polymer, Ember, nothing... it doesn't care)
  • No server-side coupling: it just compiles your client side code. It's up to you what you use on the server (Rails, Node, Go, Java, ASP.NET, PHP, static webserver...)

crunchicorn takes two arguments:

  1. An entry point .js for your app in a source tree consisting of ES2015 code, modules, CSS, etc.
  2. An output .js file that can be included in your final web page with a single <script src=...> element. Transpiled, resolved, validated, crunched, everything.

crunchicorn was born out of frustration with how complicated it is to get JavaScript tooling setup for real world projects.

10 second tutorial

Assuming you keep your source tree in src/, which contains ES2015 syntax code, imports, CSS, etc, and the entry point is src/myapp.js.

This single command (no config necessary) will do everything to validate, transpile, resolve modules, drop dead code, and compress into a single file:

$ crunchicorn src/myapp.js out/myapp.js

The resulting file is now ready to be used directly in your web-app. It will include all dependencies and even inject your CSS:

<script src="myapp.js"></script>

Voila. No config - it just worked!

Example projects

Here

File watching

You can leave crunchicorn running and it will automatically rebuild whenever it notices any files have changed:

$ crunchicorn --watch src/myapp.js out/myapps.js

Install

Install globally:

$ npm install -g crunchicorn

Alternatively, install just for your current project:

$ npm install --save-dev crunchicorn

Or in package.json:

{
  "dependencies": {
     "crunchicorn": "*"
  }
}

Note: If not installed globally, you'll need to include node_module/.bin in your path

Reference

For help:

$ crunchicorn --help

Under the hood