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

netlify-plugin-form-submissions

v0.1.4

Published

A Netlify plugin to fetch all form submission on a Netlify site, and stash them as JSON files ready for the build to use.

Downloads

19

Readme

Netlify Plugin - Form Submissions

This plugin adds the ability to fetch all submissions made to Netlify Forms in your site and stash them as JSON files before your build runs making the data available to your static site generator at build time.

Overview

This plugin uses the Netlify API to request the data submitted to your forms. It can be configured to request the data from all forms, or from forms with specific names.

You can also configure this plugin to present the gathered data in the appropriate location, so your chosen static site generator can leverage it during the build.

A demo to explore and to clone

  • Demo site: https://demo-netlify-plugin-form-submissions.netlify.app/
  • Demo repo: https://github.com/philhawksworth/demo-netlify-plugin-form-submissions

Installation

To include this plugin in your site deployment:

1. Add the plugin as a dependency


# Add the plugin as a dependency of your build
npm i --s netlify-plugin-form-submissions

2. Add the plugin and its options to your netlify.toml

This plugin will fetch the submission to specified forms and stash the data prior to the execution of the build command you have specified in your Netlify configuration. You can choose which forms you want get the submission for, or just get them all by adding some config in the netlify.toml config file. The plugin will discover all the form present in your site.

# Config for the Netlify Build Plugin: netlify-plugin-form-submissions
[[plugins]]
  package = "netlify-plugin-form-submissions"

  [plugins.inputs]
    # Get submissions for specific forms
    # e.g. "form-name"
    # e.g. ["form-name-1", "form-name-2"]
    # e.g. "ALL"
    # default: "ALL"
    formNames = "my-snazzy-form"

    # the folder to receive a json file for each form
    dataDirectory = "site/_data"

3. Grant access via the Netlify API

The plugin uses the Netlify API to access your form submissions data and requires an access token to be stored as a site environment variable.

  1. Visit your Netlify User Settings to create a new Personal access token
  2. Create a NETLIFY_AUTH_TOKEN environment variable in your site dashboard containing this access token.
  3. For local development, you may also wish to specify this environment variable in a local .env file (remember to add your .env file to your .gitignore)