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

jsonscript-express

v0.5.0

Published

Express middleware for batch processing using JSONScript

Downloads

6

Readme

jsonscript-express

Express middleware for batch processing using JSONScript.

Build Status npm version Code Climate Coverage Status

Install

npm install jsonscript-express

Getting started

Sample express app:

var express = require('express');
var app = express();
var bodyParser = require('body-parser');
var jsonscript = require('jsonscript-express');

// app needs body parser for JSON even if no endpoint uses it.
// it is needed for JSONScript middleware
app.use(bodyParser.json());

app.get('/api/resource/:id', function (req, res) {
  // ...
  res.send(data);
});

app.post('/api/resource', function (req, res) {
  // ...
  res.send(result);
});

/**
 * The line below adds JSONScript interpreter on the endpoint '/js'
 * that allows processing any scripts combining existing enpoints
 */
app.post('/js', jsonscript(app, { basePath: '/api' }));

app.listen(3000);

Now you can send POST requests to /js endpoint with the body containing the script and an optional data instance that will be processed by JSONScript interpreter. For example, with this request:

{
  "script": {
    "res1": { "$$router.get": { "path": "/resource/1" } },
    "res2": { "$$router.get": { "path": "/resource/2" } }
  }
}

the response will be a combination of two responses (both requests are processed in parallel):

{
  "res1": {
    "statusCode": 200,
    "headers": { /* response headers for the 1st request */ },
    "request": { "method": "get", "path": "/resource/1" },
    "body": { /* response body 1 */ }
  },
  "res2": {
    "statusCode": 200,
    "headers": { /* response headers for the 2nd request */ },
    "request": { "method": "get", "path": "/resource/2" },
    "body": { /* response body 2 */ }
  }
}

If option processResponse: "body" were used the result would have been:

{
  "res1": { /* response body 1 */ },
  "res2": { /* response body 2 */ }
}

JSONScript also supports sequential evaluation, conditionals, data manipulation, functions etc. So you can implement an advanced logic in your script and it will be executed in the server without sending responses of individual requests to the client.

See JSONScript Language for more information.

API

jsonscript(Express app [, Object options]) -> Function

Create express route handling function to process JSONScript. Both the script and the data instance should be properties of the request body:

{
  "script": {
    // JSONScript, can be an array
  },
  "data": {
    // data instance that can be used from the script,
    // can be array
  }
}

Options

Defaults:

{
  routerExecutor: 'router',
  basePath: '',
  processResponse: undefined,
  jsonscript: { strict: true },
  Promise: undefined
}
  • routerExecutor: the name of the executor (the value of "$exec" keyword in the instruction) used to access Express router, "router" is used by default.
  • basePath: the path used as a prefix to paths in the script $exec instruction arguments.
  • processResponse: possible values:
    • "body" - return only response body if status code is < 300, throw an exception otherwise.
    • function - custom function to process the response object, can throw an exception or return the object to be used as the result.
  • jsonscript: options passed to JSONScript interpreter jsonscript-js.
  • Promise: an optional Promise class, the native Promise is used by default.

License

MIT