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

@ryfylke-react/proxy-signal

v1.0.4

Published

Simple reactive signals for React

Downloads

15

Readme

@ryfylke-react/proxy-signal

Simple proxy signals for React

This is not intended for real use. This was just a fun experiment for javascript proxies and creating a super simple (& naive) state library. Use at your own risk.

Example

import {
  createSignal,
  useSignal,
} from "@ryfylke-react/proxy-signal";

const counterSignal = createSignal(0);

export function App() {
  const count = useSignal(counterSignal);

  return (
    <button onClick={() => (count.value += 1)}>
      {count.value}
    </button>
  );
}

Computed values

Subscribe to a computed signal value.

const state = createSignal({
  search: "",
  count: 0,
});

export function CounterButton() {
  // Will only rerender if `prevState.count !== newState.count`
  const count = useComputed(state, ({ count }) => count);

  return (
    <button
      onClick={() => {
        // Should be a new reference when signal is an object
        state.value = {
          ...state.value,
          count: count + 1,
        };
      }}
    >
      {count}
    </button>
  );
}

Automatic effects

Create effects with automatic dependency detection.

signalEffect(() => {
  console.log(
    "This will log anytime search changes: ",
    searchSignal.value
  );
});

// or tied to a component
function Counter() {
  useSignalEffect(() => {
    console.log(
      "This will log anytime search changes, while component is mounted: ",
      searchSignal.value
    );
  });
}

The effect will run once initially (twice in StrictMode) to catch dependencies. If a dependency is conditionally accessed, it might not be picked up. To fix this, just access any conditional dependencies at the top of the effect:

signalEffect(() => {
  searchSignal.value;
  if (someCondition) {
    console.log(searchSignal.value);
  }
});