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

@rohhittt/jist

v1.0.2

Published

Expressive JSON generator for generating JSON responses easily

Downloads

12

Readme

Jist

Rendering engine for rendering js files.

Why

Your JSON API route handlers / controllers can get cluttered with view logic(the logic that creates / builds the response JSON object). It can be nice to separate out response generation / build logic once the handler has fetched the data. Jist can help you transform this:

var express = require('express');
var router = express.Router();
var myService = require('./my-service');
var _ = require('lodash');

router.get('/', function(req, res, next) {
  myService.getPeople().then(function(people) {
    return people.map(function(person) {
	  person.pick(['a', 'b', 'c']);
	  person.d = (person.a + person.b) / person.c;
    });
  }).then(res.json.bind(res));
});

into

var express = require('express');
var router = express.Router();
var myService = require('./my-service');
var jist = require('jist');

router.get('/', function(req, res, next) {
  myService.getPeople().then(function(people){
    json.render('index', {
      people: people
    });
});

and

// views/index.jist
var _ = require('lodash');

return people.map(function(person) {
  person.pick(['a', 'b', 'c']);
  person.d = (person.a + person.b) / person.c;
});

This encourages reusability of view logic as well. Partials are coming soon.

Installation

npm install --save @rohhittt/jist

Usage

Express

In your app.js

var express = require('express');
const app = express();

var jist = require('jist');
jist.register(app);
app.set('views', path.join(__dirname, 'views'));

And you are done!

Just start creating .jist files in your views directory and call res.render(filePath, scope), where

filepath Is the filepath of your jist template you want to render with

scope Is the scope you want in your template. For eg. if you call

res.json('index', {
  a: 1,
  b: 2,
  c: true,
  _: require('lodash')
}`

Inside of your template, a, b, c, _ will be present as local variables.