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

view-layer

v0.6.0

Published

View Layer Server for rendering templates in support of a more featured backend server.

Downloads

49

Readme

view-layer

Just a humble little Express Wrapper, intended to gradually formalize a pattern I'm exploring where Node merely serves as a template renderer, with all genuine server work done elsewhere. The implication here is that I do not wish to write the bulk of my server code base in Node, however it's value as a primary front end language is undeniable. By abstracting all templating to a Node Server, we can get the best of the front end ecosystem without losing the stability and maturity of existing backend ecosystems.

npm install view-layer

API

Initialising

var viewLayer = require("view-layer");

var app = viewLayer();

Routing

var jade = require("view-layer/jade"); // A simple Jade Wrapper

app.route("/", jade("some-template.jade"));

app.route(path: string, handlerFunction: (args) -> string)

All routes are GETs, parsed for JSON which is parsed to the handler function. Handlers return strings which are then rendered to the request. Some examples of wrappers can be found in "view-layer/jade" and "view-layer/react-wrapped"

Listening

app.listen(4000);

app.listen(port: number, host: string, backlog: number, callback: () -> any)

Start listen for requests. This is just a wrapper for express().listen, which is in turn a wrapper for http.Server.listen

License

Copyright (c) 2015 Offsider, under the MIT License