New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

react-ssg-netlify-forms

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

react-ssg-netlify-forms - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1

2

package.json
{
"name": "react-ssg-netlify-forms",
"version": "1.0.0",
"version": "1.0.1",
"description": "A turn-key wrapper to seamlessly enable Netlify Forms in React-based SSGs (Next, Gatsby, etc..)",

@@ -5,0 +5,0 @@ "main": "./build/index.js",

@@ -1,2 +0,2 @@

# React Netlify Form
# React SSG Netlify Form

@@ -18,7 +18,7 @@ A drop-in all-in-one solution for getting Netlify Forms on React-based SSGs

Simple form usage (https://react-netlify-form.demo.jon.fm)
Simple form usage (https://react-ssg-netlify-forms.demo.jon.fm)
```jsx
import React, { useState } from "react"
import { navigate } from 'gatsby'
import NetlifyForm from 'react-netlify-form'
import NetlifyForm from 'react-ssg-netlify-forms'

@@ -59,7 +59,7 @@ const IndexPage = () => {

Yarn: `yarn add react-netlify-form`
Yarn: `yarn add react-ssg-netlify-forms`
NPM: `npm i react-netlify-form`
NPM: `npm i react-ssg-netlify-forms`
Then import into your React code where desired (shown above): `import NetlifyForm from 'react-netlify-form'`
Then import into your React code where desired (shown above): `import NetlifyForm from 'react-ssg-netlify-forms'`

@@ -84,3 +84,3 @@ ## Usage

This is the natural progression if using the example above where form state is managed in a single object (which also makes having a generic `onChange` handler possible 😁). The key reason for this is so that you can employ your own validations and other UX flow concerns with the form data at your fingertips. This is better illustrated in a [slightly more complicated example](https://github.com/jon-fm/react-netlify-form-demo/blob/master/src/pages/medium.js).
This is the natural progression if using the example above where form state is managed in a single object (which also makes having a generic `onChange` handler possible 😁). The key reason for this is so that you can employ your own validations and other UX flow concerns with the form data at your fingertips. This is better illustrated in a [slightly more complicated example](https://github.com/jon-fm/react-ssg-netlify-forms-demo/blob/master/src/pages/medium.js).

@@ -93,3 +93,3 @@ **formName** - a _required_ prop - You may make this whatever you'd like - this is what will show up in the Netlify UI as the 'name' label for your form. This name is also what's referenced in the Subject field of Forms notifications emails.

_A note: **preSubmit** is where you'd want to manifest any sort of form validations or checks you'd like to run. Please see [this example](https://github.com/jon-fm/react-netlify-form-demo/blob/master/src/pages/medium.js) for an idea of what that might look like_
_A note: **preSubmit** is where you'd want to manifest any sort of form validations or checks you'd like to run. Please see [this example](https://github.com/jon-fm/react-ssg-netlify-forms-demo/blob/master/src/pages/medium.js) for an idea of what that might look like_

@@ -96,0 +96,0 @@ **postSubmit** - an _optional_ prop - A function that the `<NetlifyForm>` component will call _after_ submitting the form data to Netlify. This may be an Async function. This function will not receive arguments.

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc