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

@terribleplan/next-cloudflare

v0.0.1

Published

A way to build next.js apps for cloudflare workers

Downloads

2

Readme

@terribleplan/next-cloudflare

This is pretty rough right now, but it works and can hopefully used to foster discussion in the next.js project around a different/better/additional serverless interface.

Quickstart

  1. You must be using my fork of next.js.
    1. git clone https://github.com/terribleplan/next.js
    2. yarn && pushd packages/next-server && npm link && popd && pushd packages/next && npm link && npm link next-server && popd
  2. Install this package to your project
    1. yarn add @terribleplan/next-cloudflare
  3. Build things
    1. npx next build && npx next-cloudflare

Usage

This package is usable as an npm module as well as a CLI.

CLI

--input

The project directory that houses the .next build output directory. Defaults to whatever directory the command is invoked from.

This is passed as cwd to the programmatic API

--output

Where to write the output to. Defaults to cloudflare-bundle.js in the input directory (which defaults to the current working directory).

API

Usage

const nextCloudflare = require('@terribleplan/next-cloudflare');

const bundleString = await nextCloudflare(options);

console.log(bundleString);

options.cwd

The project directory that houses the .next build output directory. Defaults to process.cwd().