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 🙏

© 2026 – Pkg Stats / Ryan Hefner

jimi

v1.0.0

Published

A framework for writing modular web applications in node.js

Readme

jimi

A framework for writing modular web applications in node.js

About

Apps contain a set of (regex) URL mappings that map HTTP requests to functions called handlers. URL mappings and handlers can be stored in separate files, which are imported when the app is executed. Apps can be organised into a set of modules, each with their own URL and handler definitions. You can build quite complex apps by hooking a module's URL mappings into one of another module's URL mappings.

jimi currently uses a javascript conversion of the django template system (written by Simon Willison), which has been modified slightly to work with more recent versions of node.js. The template system can be hooked into your handlers to provide a simpler way to render your content.

To use jimi & run the example apps you must have node.js, npm and Connect installed.

Installation

To install through npm, run the following command in your terminal of choice:

npm install jimi

Get Started

Have a run through the tutorial to get a flavour of how jimi works. It'll take you 5 minutes to get your first site up and running. If it takes more than 5, I'll give you your money back.

Example Apps

Examples are be stored in the apps directory, and will give you a starting point for building your applications. Navigate to an example app directory and run:

node app.js

Then visit http://127.0.0.1:8009/ in your web browser.

Example App Structure

<app_directory>
 |
 |- app.js
 |- handlers.js
 |- urls.js
 |
 |- <module_directory>
 |   |
 |   |- handlers.js
 |   |- urls.js
 |
 |- <public_directory>
 |   |
 |   |- <public_file>.css
 |
 |- <templates_directory>
     |
     |- <base_template>.html
     |
     |- <module_directory>
         |
         |- <template>.html
         |- <template>.html

Templates don't have to be laid out this way, but the templating example uses this layout. Public content such as static files should also be placed in a folder inside your app directory. Look at some of the examples to see how they fit in.

In Development...

  • I'm considering replacing the templating system with something more lightweight as a one-to-one copy of the django templating system may not be the best way forward. This may not happen straight away though.

  • I'm also considering various node.js data modelling libraries for building the 'model' layer of jimi, so please use this repos's Issues to make suggestions

Thanks

jimi was originally based on djangode, a node.js micro-framework written by Simon Willison. The framework still uses the djangode templating system, so he deserves heaps of credit.