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

express-rendertype

v1.2.0

Published

Express middleware to (automatically) render content and errors to content-type

Downloads

21

Readme

express-rendertype

Build Status Coverage Status Dependency Status devDependency Status Downloads

Express middleware to (automatically) render content and errors to content-type

NPM

This is basically a mashup of


Installation

npm install --save express-rendertype

Usage

render = require "express-rendertype"

app = express()

Rendering content

render.auto(fallback = false, preference = ["yaml", "json", "html", "text"])

create a .rendr method on the res object, falling back to json as default

app.use render.auto "json"

res.rendr(path = "", obj)

render to json or whichever content-type the client accepts

app.get "/someroute", (req, res, next) -> res.rendr "path/to/template", obj

Rendering errors

Status code

pass an error from just a status code

app.post "/noauthroute", (req, res, next) -> next status: 401

Error library

create an error with stacktrace in context from a status code

app.put "/payme", (req, res, next) -> next render.error.fromCode 402

throw an error with message from the error library

app.get "/gatekeeper", (req, res, next) ->
  throw new render.error.LockedError "I am the keymaster"

See also: restify/errors

Objects

pass an object as the error

app.delete "/session", (req, res, next) -> next {foo: "bar", baz: "booze"}

(Fancy) Error-handling middleware

add the error-handling middleware after all routes

app.get ...
app.post ...
app.put ...
...
app.use render.FancyErrors.auto "text" if (@app.get "env") is "development"
app.use render.Errors.auto()

render.FancyErrors.auto(fallback, preference, log)

render.Errors.auto(fallback, preference, log)

Errors and FancyErrors are the same, except FancyErrors will log the stack to all content-types. FancyErrors even has a nice code excerpt when rendered to HTML.

app.use render.Errors.auto "html", ["html", "json"], console.log

MIT Licensed. (C) 2016 doublerebel