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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@formbuilder-cloud/create

v0.1.1

Published

npm create @formbuilder-cloud: copy a formBuilder Cloud example (React, Next.js, Vue, plain HTML or a Node webhook receiver) into a new directory with a .env template. No network, no install, no telemetry.

Readme

@formbuilder-cloud/create

npm create @formbuilder-cloud starts a formBuilder Cloud project from a template: React, Next.js, Vue, plain HTML or a Node webhook receiver. It copies the template into a new directory and writes .env from the template's .env.example. It installs nothing, makes no network request and sends no telemetry.

Version 0.1.0, not published yet. npm create @formbuilder-cloud works once Kevin publishes this package and the @formbuilder-cloud/adapter and /sdk packages the templates install (RELEASING.md). In this repository, run the built bin directly: npm -w create run build && node create/dist/bin.js my-app --template react.

npm create @formbuilder-cloud@latest my-app -- --template react
cd my-app
# fill in .env: FORMBUILDER_FORM_ID, FORMBUILDER_COLLECTION_KEY (README.md, "Environment")
npm install
npm run dev

npm runs this package's create-formbuilder-cloud bin, so npx @formbuilder-cloud/create my-app --template react does the same. With npm, options go after --.

| Template | What | |---|---| | react | React (Vite) with the adapter | | nextjs | Next.js (App Router) with the SDK and the adapter | | vue | Vue 3 (Vite) with the adapter | | html | Plain HTML with the embed script (a tiny Node server) | | node-webhook | Node webhook receiver (signature verification, no dependencies) |

Each template is a copy of examples/<name> in the formbuilder-cloud repository, taken when this package is built. Each runs with only FORMBUILDER_* variables; examples/README.md has the full table.

Options

create-formbuilder-cloud [directory] [--template <name>]
  -t, --template <name>  the template (asked for when omitted in a terminal)
      --list             print the template names, one per line
  -h, --help             the usage
  -v, --version          the version
  • directory defaults to formbuilder-cloud-<template>. It must not exist, or be empty. The new package.json is named after it.
  • Without --template, it asks in a terminal. Without a terminal (CI, an agent), it exits 2 with the usage and creates nothing.
  • Exit codes: 0 done, 1 refused (the directory is not empty), 2 usage (an unknown template or option).
  • .env is written with mode 0600, and each template's .gitignore excludes it.

Licence

UNLICENSED: proprietary. Copyright (c) 2026 Kevin Chappell, all rights reserved. You may use it only with the formBuilder Cloud service and under that service's terms (LICENSE). Each template's README.md carries its notice into the project it creates: Copyright (c) 2026 Kevin Chappell. All rights reserved. You may copy and modify the example/template code in this directory into your own applications that use the formBuilder Cloud service (decision-register item 39, option C). The templates install jQuery and formRender from npm, and those keep their own MIT licences.