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-spa

v0.0.2

Published

Static sites are great until you want html5 push state urls. Then they suck because every path besides the index breaks on external entry.

Downloads

123

Readme

express-spa

Static sites are great until you want html5 push state urls. Then they suck because every path besides the index breaks on external entry.

In case that didn't make any sense imagine the following sequence.

  1. User comes to site (GET /).
  2. User navigates within the page, and the client app silently changes the url to /some/page.
  3. User loves the page and shares it with a friend.
  4. Friend clicks on link (GET /some/page).
  5. The friend gets an error (404), because the server doesn't know about client-side routing.

With express-spa this is fixed.

Example

var express = require('express')
var spa = require('express-spa')

var app = express()
app.use(spa())

All requests for html regardless of path will stream the index html file. The filepath defaults to index.html in the root of the project folder. Absolute paths and paths relative to the project folder are supported.

// project/server/app.js

spa()                           // project/index.html
spa('views/index.html')         // project/views/index.html
spa(__dirname + '/main.html')   // project/server/main.html

Rest assured project folder does not mean process.cwd(). It means project folder.

Replacements

You can also pass in an object of replacements. This way you don't need a view rendering engine to inject a couple variables. Rendering with jade can take up to 200ms instead of like 6ms.

<body>
  <script>window.VERSION = '$VERSION';</script>
</body>

Be careful to avoid unwanted matches.

spa({ '$VERSION': '1.1' })

The streamed markup will have the replacement.

<body>
  <script>window.VERSION = "1.1"</script>
</body>

You can specify both file path and replacements.

spa('filename.html', { key: 'value' })

Notes

Install with npm.

$ npm install express-spa --save

For max performance check out Divshot to serve static sites off a CDN.

License: MIT