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

vue-netlify-form

v0.3.0

Published

This component was created to simplify submission to [Netlify Forms](https://docs.netlify.com/forms) and help catch common mistakes.

Downloads

29

Readme

vue-netlify-form

This component was created to simplify submission to Netlify Forms and help catch common mistakes.

Features

  • Validates presence of form and field names. Form name is a required prop. The presence of field names is validated during development (by checking NODE_ENV != "production) and emits a console warning like Missing Netlify form field named: Email if a form field lacks a name.
  • Submits form data to Netlify using @nuxt/axios.
  • Passes form lifecycle state through scoped slots.

Usage

<template>

  <netlify-form name='Contact' :form='form'>
    <template #default='{readonly, submitting, submitted}'>

      <p v-if='submitted'>Thanks for your submission</p>

      <input
        name='Email'
        placeholder='Email'
        v-model='form.Email'
        :readonly='readonly'>

      <button>
        {{ submitting ? 'Submitting' : 'Submit' }}
      </button>

    </template>
  </netlify-form>

</template>

<script>

export default {
  data: function() {
    form: {
      Email: ''
    }
  }
}

</script>

Props

| Name | Default | Description | | ---- | ------- | ----------- | | name | required | The name of the form. This will be how the form shows up within the Netlify Forms dashboard | | form | required | The form data as key/value pairs. This is what your form fields are updating on input. You may want to title case the keys as these are what are displayed within the Netlify Forms dashboard | | endpoint | / | Where the form should submit to. On production, the form should POST to the root of your site. While dev-ing locally, you may want to pass the hostname of your Netlify app here so you can post to it from your localhost. This also reads from process.env.NETLIFY_FORMS_ENDPOINT. |

Notes

CORS when using endpoint

If you're going to use the endpoint prop to submit to your production endpoint from localhost, you should add something like the following to _headers to allow those requests.

/
  Access-Control-Allow-Origin: http://localhost:3000
  Access-Control-Allow-Methods: POST
  Access-Control-Allow-Headers: content-type