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 🙏

© 2025 – Pkg Stats / Ryan Hefner

nodetiles

v0.0.1

Published

Nodetiles Build Tool

Readme

Nodetiles framework tool.

Getting Started

Install this Grunt plugin with: npm install -g ntiles

To test installation, run the ntiles command. You should see something like this:

screenshot

Commands

All commands are prefixed with ntiles in your terminal. For example the command init below would be executed like this:

$ ntiles init

Tasks are defined inside the grunt-nodetiles project, but also borrowed from other grunt projects: grunt-contrib & grunt-jasmine-task

If you have problems with borrowed tasks, please file issues on the respective projects.

Scaffolding

These commands will build out files for you.

init (ntiles)

Creates a bare boilerplate project.

init:tutorial (ntiles)

Run bbb init before this command

Creates a boilerplate which contains the tutorial.

init:todomvc (ntiles)

Run bbb init before this command

Creates a boilerplate which contains the TodoMVC application that utilizes LayoutManager.

init:module (ntiles)

Run bbb init before this command

Creates a new module in the app/modules directory.

Maintenence

These commands help you maintain your project.

lint (grunt)

Ensures all your code conforms to JSHint.

list (bbb)

Shows a tree of your application's modules and dependencies.

Build

These commmands help you build your application.

debug (bbb)

Lints all your JavaScript, compiles all your templates to JST (JavaScript Templates), builds your application using RequireJS build tool (figures out dependencies and concatenates all files), and then finally concatenates the templates and application together. This task also swaps out RequireJS for Almond (signficantly smaller filesize AMD manager).

release (bbb)

Everything that debug command does, except the final tasks here are minified CSS and minified JavaScript.

clean (grunt-contrib)

Removes all files inside dist/ directory.

handlebars (grunt-contrib)

Compiles handlebars templates - this requires setup.

jst (grunt-contrib)

Compiles all templates as underscore template functions and outputs them to dist/debug/templates.js.

less (grunt-contrib)

Compiles LESS stylesheets.

mincss (grunt-contrib)

Minifies your CSS into dist/release/index.css.

requirejs (bbb)

Builds out your application using the defaults specified into the root grunt.js file.

server (bbb)

Will by default run with normal files perfect for development and debugging.

server:debug (bbb)

This command serves the same files excepts that your application is mapped to the dist/debug directory. This is mostly useful for detecting issues with the build, since files are not minified.

server:release (bbb)

This command will serve the same was debug except mapping to dist/release instead. This setup is how your application should be deployed.

styles (bbb)

Parses a valid CSS file for @imports and concatenates them into an output file. Will automatically build stylus files as it encounters them.

Sample configuration:

styles: {
  // Output stylesheet file.
  "dist/debug/index.css": {
    // Main CSS source file, containing the @imports.
    src: "assets/css/index.css",

    // Relative path for `@imports`.
    paths: ["assets/css"],

    // Add additional stylesheets.
    additional: ["assets/css/production-fixes.css"]
  }
},

Development

If you wish to contribute or just want to install from source, simply run the following commands:

# Clone the repository.
git clone git://github.com/codeforamerica/grunt-nodetiles.git

# Change directory into it.
cd grunt-nodetiles

# Update all the submodules recursively.
git submodule update --init --recursive

# Allow ntiles to be globally accessible.
sudo npm link

License

Copyright (c) 2012 Tim Branyen (@tbranyen)
Licensed under the MIT license.