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

prunt

v0.1.3

Published

Like grunt, but simpler

Downloads

2

Readme

Like grunt, but simpler

A prunt is a small blob of glass fused to another piece of glass to help provide a firm grip in the absence of a handle. -- Modified from Wikipedia.

Prunt is a small build utility similar to grunt. It have several aims.

  • Promise/A-based workflow
  • Declarative deta transformation
  • Use your favorite CLI

Current features:

  • Concatenate files
  • Compile coffee-script
  • Minify JavaScript
  • Minify CSS

Install

npm install prunt

.then - promise/A-based workflow

Usually our source code went through several steps. Prunt use Primise/A-based API to make this simpler.

read('src/*.coffee')
  .then(step1)
  .then(step2)
  .done(write)

For example we might concat, compile, and minify source codes

read('src/*.coffee')
  .then(concat)
  .then(compile)
  .then(uglify)
  .done(write)

We can even go further with this concept

prunt = require 'prunt'

coffeeFilter = prunt.filter (file) ->
  file.filename.match /.coffee/
compileCoffee = do prunt.coffee

cssFilter = prunt.filter (file) ->
  file.filename.match /.css/
minifyCSS = do prunt.less

sourceCodes = prunt.read 'src/*'

# Coffee-script workflow
sourceCodes
  .then(coffeeFilter)
  .then(compileCoffee)

# Less workflow
sourceCodes
  .then(cssFilter)
  .then(minifyCSS)

Declarative deta transformation

Every plug-in for prunt is

  • a) a function that accept an array of file instances
  • b) a factory function that returns (a)

Example: Let's write a plugin that appends licence info to the end of source codes.

addLicence = (files) ->
  files.forEach (file) ->
    file.content += '''\n
    Copyright (C) 2013 Hao-kang Den
    Permission is hereby granted, free of charge, to any person bla bla bla...
    '''
  files

read('src/*.coffee')
  .then(addLicence)
  .done(write)

We can also write a factory method to accept several kind of licence declaration.

addLicenceFactory = (type = 'MIT') ->
  licence = undefined
  switch type
    when 'MIT'
      licence = 'bla bla bla'
    when 'GPL'
      licence = 'bla bla bla'
  (files) ->
    files.forEach (file) ->
      file.content += licence
    files

addMITLicence = addLicenceFactory 'MIT'

read('src/*.coffee')
  .then(addMITLicence)
  .done(write)

Use your favorite CLI

Prunt does not come with a CLI. Use anything you like instead. For coffee-script users, Cakefile is a very good place it.

# Cakefile
{read} = prunt = require './index'

concat = prunt.concat {filename: 'index.coffee'}
compile = do prunt.coffee
write = do prunt.write

task 'build', 'concat, compile, and write them back to disk', ->
  read('src/*.coffee')
    .then(concat)
    .then(compile)
    .done(write)

Development

build cake build test npm test or mocha

Coming soon:

  • Clean files and folders
  • Compile Sass
  • Compile LESS
  • Please vote for new features at issue pages

Pending for requests:

  • jshint
  • csslint
  • coffeelint
  • handlebar
  • htmlmin
  • imagemin
  • Stylus
  • jade

Licence (MIT)

Copyright (C) 2013 Hao-kang Den

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.