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

@yawnxyz/somewhat-questionable

v0.44.1

Published

Vercel builder for Sapper with SSR enabled

Downloads

2

Readme

vercel-sapper (a.k.a. now-sapper)

Vercel builder for Sapper with SSR enabled

What's in it for you?

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

Automatic configuration

Run npx vercel-sapper on an existing project.

Or create a new project with npx vercel-sapper my-project

🧪 This feature is experimental, let us know what you think => https://github.com/thgh/vercel-sapper/pull/47

Manual configuration

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

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

To install a working example of a vercel-sapper template ready for deployment or development, see the examples directory.

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

Example .vercelignore :

__sapper__
node_modules

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

4. Deploy to Vercel

Run vercel to build and deploy your project. You can install the vercel cli by running npm i -g vercel

Run sapper dev for local development. vercel dev does not work for local development

Options

Node.js version

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

Example package.json

{
  "engines": {
    "node": "12.x"
  }
}
Include files outside the __sapper__ folder

The static folder is always hosted on the Vercel CDN. Before v0.42 it was also included in the lambda function. Here is how to include it again:

Example vercel.json

{
  "version": 2,
  "builds": [
    {
      "src": "package.json",
      "use": "vercel-sapper",
      "config": {
        "include": ["static"]
      }
    }
  ]
}
Memory Configuration

You can change the amount of memory your lambda runs with. This is useful to optimise costs.

Note that reducing memory also reduces the amount of CPU available to the lambda, so try some values before you optimise too much.

{
  "version": 2,
  "builds": [
    {
      "src": "package.json",
      "use": "vercel-sapper",
      "config": {
        "memory": 3008
      }
    }
  ]
}

Where builds[].config.memory can be any value allowed by AWS Lambda.

No-build usage

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

Recommended .vercelignore:

__sapper__/dev
__sapper__/export
cypress
node_modules

Example vercel.json

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

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 Vercel with minimal config. New features should be in line with other builders like now-next. Please see the now Developer Reference for more info.