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

voila

v0.1.0

Published

best asset manager one can get in nodejs

Downloads

23

Readme

voila

best asset manager one can get in nodejs (at least we hope so)

Why does voila exist?

We needed an asset manager which meets the following condition:

  • Optimized for runtime such that major processing occurs before deployment, not during app launch.
  • Support CDNs wth the node.js server as origin for assets with md5 extended asset names.
  • Process all major engines like coffee, stylus, less, ejs etc..
  • Provide a helper for asset path which doesn't suck

Under the hood we use mincer which did the heavy lifting.

Voila is the brainchild of Pavan Kumar Sunkara

Installation

Go to you app root directory and run

npm install --save voila

Usage

In your connect/express application

var express = require('express')
  , voila = require('voila')
  , app = expres();

var conf = {
  development: {},
  production: {
    serve: "http://assets.yoursite.com/assets"
  }
}

app.use('/assets', voila(__dirname + '/../', conf[process.env.NODE_ENV])

That pretty much sets up the pipeline. Defaul directory structure is as follows

app
├─┬ assets
│ ├── css
│ ├── js
│ └── img
└─┬ public
  └── assets
  • app/assets should be ignored in .npmignore (which is generally used for nodejs deployment)
  • app/public/assets should be ignored in .gitignore (which is used for committing to repo)

In your package json add the following:

"scripts": {
  "assets": "rm -rf public/assets/* && voila -p http://assets.yoursite.com/assets"
}

This script should be activated before you publish to production, npm run-script assets. It creates the preprocessed files in /public/assets

License

MIT/X11

Bug Reports

Report here.