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

serender

v1.0.0

Published

Server side rendering Express middleware

Downloads

4

Readme

Serender

Serender is a tiny middleware for Express that takes care of rendering client-side apps on the server, making your content load first before your JavaScript code takes over.

Package Version Package Downloads Code Climate Dependencies Status

Demo screencast: http://youtu.be/ZvpjkA7q7pM

Installation

$ npm install serender --save

Usage

Front-end frameworks generally rely on the hashchange event in the browser, that's why you always have a # in the url. If you managed to get rid of it, then you've definitely defined some routes in your Express app so your users won't see a not found error when they refresh the page:

// app.js
var express = require('express')
var serender = require('serender')

var app = express()

app.set('port', process.env.PORT || 3000)

app.get('/', serender, function(req, res) {
  res.sendFile('index.html', { root: 'client/dist' })
})

app.get('/company', serender, function(req, res) {
  res.sendFile('index.html', { root: 'client/dist' })
})

app.get('/work', serender, function(req, res) {
  res.sendFile('index.html', { root: 'client/dist' })
})

// Server the cient-side app's static files (CSS, JS, Images...)
// from the 'client/dist' folder
app.use(express.static('client/dist'))

app.listen(app.get('port'))

Notice how I'm using router.use(express.static('client/dist')) after the routes! This will server our static assets (CSS, JS, Images...) but we don't want our index.html page to be served with them.

Cookies

Serender handles cookies very well! Your authenticated users will see the content they must see even if they disable JavaScript completely.

That's it! You can now focus on building you client-side app without being worried about any SEO issues, or clients with no JS!

How does it work?

Serender uses Zombie under the hood, which is a headless simulated browser for testing client side code.

When you use it as the first middleware for your routes, Serender spins up a new Zombie (browser) instance for each new request, and makes it load the same exact page that the user is asking for. This might look like creating an infinit loop, but Serender adds a value to the browser headers making it skip itself and pass the new request to the next middleware.

Zombie then loads the page, fetches all the assets, and runs the JavaScript code wich will then take care of fetching data from you API and rendering the page.

As soon as Zombie finishes loading the page, Serender will take the final HTML output and send it back to the user.