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-deno/ci

v0.1.0-2ce1691e1696d2af7abb5b0fc644eb1407152cfe

Published

Community builder for using deno on the ZEIT Now platform

Downloads

17

Readme

now-deno

Deno builder for Vercel - run Deno on vercel. 🦕 + λ = ❤️

This builder allows you to run Deno as a lambda on vercel.

Usage

If you're unfamiliar with vercel runtimes, please read the runtime docs first. This runtime can be used like any other Community Runtime.

// vercel.json
{
  "functions": {
    "api/**/*.{j,t}s": {
      "runtime": "[email protected]"
    }
  }
}

Note: You need vercel v17.x or above to use the above configuration.

// api/hello.ts
import {
  APIGatewayProxyEvent,
  APIGatewayProxyResult,
  Context,
} from 'https://deno.land/x/lambda/mod.ts';

export async function handler(
  event: APIGatewayProxyEvent,
  context: Context
): Promise<APIGatewayProxyResult> {
  return {
    statusCode: 200,
    body: `Welcome to deno ${Deno.version.deno} 🦕`,
    headers: {
      'content-type': 'text/html; charset=utf-8',
    },
  };
}

That's the simplest way to use this runtime!

Advanced usage

Specific Deno version

To use a specific version of Deno you can specify a environment variable in your vercel.json:

// vercel.json
{
  "functions": {
    ...
  },
  "env": {
    "DENO_VERSION": "0.42.0"
  }
}

Unstable mode

To use Deno's unstable mode you can specify the environment variable DENO_UNSTABLE in your vercel.json:

// vercel.json
{
  "functions": {
    ...
  },
  "env": {
    "DENO_UNSTABLE": "true"
  }
}

TS Config

To pass a custom config, you can specify the variable DENO_CONFIG in your now.json:

// now.json
{
  "functions": {
    ...
  },
  "env": {
    "DENO_CONFIG": "tsconfig.json"
  }
}

Custom pre-package script

You can place a build.sh function in the root of your deploy directory. This will be executed before the function is packaged up.

vercel dev

vercel dev is currently only supported on macOS and Linux. It is not supported on Windows.

If you have have deno installed in your path then you can use vercel dev with this runtime. It should work just like any other runtime.

Credits

This was only possible due to the great work of Andy Hayden who made the first attempts at running deno in a lambda function.