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

svelte-well-formed

v0.0.1

Published

Simple library for svelte

Downloads

2

Readme

svelte-well-formed

Another form library for Svelte, svelte-well-formed aims to create forms that are accessible and customisable, while also catering for common requirements like validation.

Installation

As usual, for a Svelte project:

npm install --save-dev svelte-well-formed

Usage

Import the form component:

import Form from 'svelte-well-formed';

Configure some fields and define a submit handler:

const fields = [
    {
        name: 'username',
        label: 'Username',
    },
    {
        name: 'password',
        label: 'Password',
    },
];

const handleSubmit = async values => {
    // Do something asynchronously here.
    // Or just log values.
    console.log('Username:', values.username);
    console.log('Password:', values.password);
};

Enjoy!

Client-side validation

Client-side validators can be added to fields under the validators property. The validator must be a function with signature

(value: string) => [<value is true: boolean>, <error message: string>]

If valid errorMessage will be ignored; if !valid && !errorMessage, then a default error message will be substituted.

const myValidator = value => [value.length >= 8, 'Password is too short.'];
const fields = [
    {
        name: 'password',
        label: 'Password',
        validators: [myValidator],
    },
    // ...
];

Alternatively, you can use one of the built-in validators included with this module:

import {isRequired, isValidPassword} from 'svelte-well-formed/lib/validators';

field.validators = [isRequired, isValidPassword];

See ./lib/validators.js for more available validators.

Server-side validation

Of course, client-side validation is only half of the problem. Most of the time we also need to validate on the server. You can indicate the success or failure of a form submission with the return value (or returned promise's resolved value) of the on:submit handler.

If everything succeeded, the submit handler needn't return anything:

const onSubmit = values => undefined;

To indicate that field-specific errors were encountered:

const onSubmit = async values => {
    // ... do stuff ...
    return {
        errors: {
            username: 'A user with that username already exists.',
        },
    };
};

Errors which are not field-specific can be used as well/instead, using the formError property:

const onSubmit = async values => {
    // ... do stuff ...
    return {
        errors: {
            // ...
        },
        formError: 'There was a problem processing your request.',
    };
};

Finally, if your submit handler throws an error or returns a promise which rejects, the form will act as if you returned a generic formError:

const onSubmit = values => {
    throw new Error('Uh oh!');
};

We don't recommend (intentionally) using this final approach; it's merely there to protect your UI from an unexpected failure.