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

use-create-signal

v1.0.0

Published

This is a package with use-create-signal. Hook that improves default useState to make it into Signal apprach

Downloads

234

Readme

use-create-signal

Implements createSignal from Solid-JS for React-JS

Lightweight package that fixes most useState problems:

  • value is locked in scope
  • setState doens't return value
  • parallel updated only possible with predicates

How to use

Just like you use useState

But value is a getter function

type DefaultValueType<T> = T | (() => T);

type UseCreateSignalType<T> = (
  defaultValue?: DefaultValueType<T>
) => [() => T, (setter: SetStateAction<T>) => T, T];
const Component = () => {
  const [getter, setter] = useCreateSignal('');

  return <input value={getter()} onChange={e => setter(e.target.value)} />;
};

Or if you also need value, it's gonna be here

const Component = () => {
  const [getter, setter, value] = useCreateSignal('');

  return <input value={getter()} onChange={e => setter(e.target.value)} />;
};

Advantages

  • useCallback / useEffect and others don't require to put value in deps
  • consecutive useEffect have updated values
  • parallel useEffect have actual updated values
  • multiple child components will have actual updated values

Downsides

  • memo-components: getter is always the same function. so if you pass getter-function directly - also pass it's result

Examples

const Component = () => {
  const [getter, setter] = useCreateSignal(() => 1); // or just useCreateSignal(1). it's the same as useState

  const handleIncrement = useCallback(() => {
    const newValue = setter(getter() + 1);
    console.log('no deps required. newValue: ', newValue);
  }, []);

  const handleWowIncrement = useCallback(() => {
    const newValue = setter(old => old + 1);
    console.log('WOW. it returned value from predicate. Much wow', newValue);
  }, []);

  // these effects have values updated in between
  useEffect(() => {
    const value = getter();
    console.log(setter(value + 1)); // return 2
  }, []);
  useEffect(() => {
    const value = getter();
    console.log(setter(value + 1)); // return 3
  }, []);
  useEffect(() => {
    const value = getter();
    // parallel effects didn't get updated values
    // this does
    if (value > 2) return;

    console.log(setter(value + 1)); // won't execute
  }, []);

  return <div onClick={handleIncrement}>I was clicked {getter()} times</div>;
};
const InputWithValidation = ({ value, hasError, onValidation }) => {
  useEffect(() => {
    const isNotValid = value > 100;

    onValidation(isNotValid);
  }, [value]);

  return 'Something';
};

const MultipleInputs = ({ onErrors }) => {
  const [getFormErrors, setFormErrors] = useCreateSignal({});
  const formErrors = getFormErrors();

  const handleOnErrors = newErrors => {
    setFormErrors(newErrors);
    onErrors?.(newErrors);
  };

  return (
    <div>
      <InputWithValidation
        value={190}
        hasError={formErrors.first}
        onValidation={isValid =>
          handleOnErrors({ ...getFormErrors(), first: isValid })
        }
        // this would fail, as only last input would be validated
        // onValidation={isValid => handleOnErrors({ ...formErrors, first: isValid })}
      />
      <InputWithValidation
        value={310}
        hasError={formErrors.second}
        onValidation={isValid =>
          handleOnErrors({ ...getFormErrors(), second: isValid })
        }
      />
      <InputWithValidation
        value={90}
        hasError={formErrors.third}
        onValidation={isValid =>
          handleOnErrors({ ...getFormErrors(), third: isValid })
        }
      />
      <InputWithValidation
        value={20}
        hasError={formErrors.fourth}
        onValidation={isValid =>
          handleOnErrors({ ...getFormErrors(), fourth: isValid })
        }
      />
      <InputWithValidation
        value={290}
        hasError={formErrors.fifth}
        onValidation={isValid =>
          handleOnErrors({ ...getFormErrors(), fifth: isValid })
        }
      />
    </div>
  );
};