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

now-sapper

v0.39.2

Published

ZEIT Now 2.0 builder for Sapper with SSR enabled

Downloads

107

Readme

now-sapper

ZEIT Now 2.0 builder for Sapper with SSR enabled

What's in it for you?

  • [x] Deploy your Sapper app in 30 seconds.
  • [x] Serve all static assets from a CDN.

Basic usage

You must make 3 changes to your project to get started:

  1. Configure now-sapper as builder in now.json
  2. Export the server instance in src/server.js
  3. Ignore the local build folder __sapper__

Check out this demo project that uses this builder. It can be used as a template, or a way to verify correct usage of the following instructions.

1. Configure now-sapper as builder in now.json
{
  "version": 2,
  "builds": [{ "src": "package.json", "use": "now-sapper" }]
}
2. Export the server instance in src/server.js
const app = express() // or polka()
export default app
3. Ignore the local build folder __sapper__

Example .nowignore :

__sapper__
node_modules

Consider also ignoring the cypress folder if you are not running tests.

Options

Node.js version

You can change the Node.js version with the engines field.

Example package.json

{
  "engines": {
    "node": "12.x"
  }
}
No-build usage

Useful if you are building the project on CI, and then want to just push the compiled source.

Recommended .nowignore:

__sapper__/dev
__sapper__/export
cypress
node_modules

Example now.json

{
  "version": 2,
  "builds": [
    {
      "src": "package.json",
      "use": "now-sapper",
      "config": {
        "build": false
      }
    }
  ]
}

Troubleshooting

now dev doesn't work

True story, use sapper dev instead: https://github.com/thgh/now-sapper/issues/4#issuecomment-536189926

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Contributions and feedback are very welcome.

This project aims to enable developers to deploy to Now with minimal config. New features should be in line with other builders like now-next.