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

seorsum

v1.1.1

Published

I have problems with redux and react-redux when working with react. I want to my view and business logic to be as separate as possible. I feel like you should be able to have all your state management and business logic in separate files to your view.

Downloads

2

Readme

Seorsum

Why

I have problems with redux and react-redux when working with react. I want to my view and business logic to be as separate as possible. I feel like you should be able to have all your state management and business logic in separate files to your view.

With redux this seems to be a had task to tackle especially with react-redux. So I created a state management system to function outside the view but with easy access from inside the view, while still being able to rerender components that subscribe to that piece of state.

Usage

// Import the createStore function
import { createStore } from 'seorsum';

// Create an initial state
const initialState = {
  name: {
    first: 'John',
    last: 'Doe',
  },
  age: 50,
};

// Create the store object
const { updateState, subscribe, useStateValue } = createStore(initialState);

// Create an action
const setAge = (age: number) => {
  return updateState(draft => {
    draft.age = age;
  });
};

/* React Usage */
import * as React from 'react';
const AgeComponent = () => {
  const age = useStateValue(['age']);
  const firstName = useStateValue(['name', 'first']);
  return (
    <span>
      {firstName} is {age} years old.
    </span>
  );
};
// This component is now subscribed to the state and when the age is changed
// the component will rerender

// Calling the setAge action we created earlier will update the state
// and rerender any component that uses it
setAge(60);
// or
const AgeButtonComponent = () => (
  <button onClick={() => setAge(60)}>Set Age!</button>
);

/* Non-react usage */
// Just subscribe to a state with a callback to run
const unsubscribe = subscribe(['age'], age => {
  console.log(`Age changed! New value is ${age}`);
});
// This callback will be run every time age is changed until `unsubscribe` is run
setAge(60); // console.log: "Age changed! New value is 60"
unsubscribe();
setAge(10); // no logs

Benefits

Because it's so decoupled from the view you can test your state updates very easily without having to render any components. It also means you can test your view separately as well.

// Create an action
const setAge = (age: number) => {
  return updateState(draft => {
    draft.age = age;
  });
};

const newState = setAge(10);
expect(newState.age).toBe(10);

Asynchronous actions are possible by default so no more need for Thunk or Saga

const fetchResults = async () => {
  const results = await api.fetch();
  return updateState(draft => {
    draft.results = results;
  });
};