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

freactal-rebuild

v1.0.1

Published

This is a rebuild of the Freactal model using the new React Context. It includes several variations driven by my experience with Freactal.

Downloads

2

Readme

This is a rebuild of the Freactal model using the new React Context. It includes several variations driven by my experience with Freactal.

For the Freactal Aware

This uses the new React (16.3+) Context to manage injection/provision of state into a react DOM tree. A few notable differences:

  1. Provision is done via a component. It uses the ProviderComponent's state as its state store.
    1. the configuration for the store (actions, initializer) are passed in through properties.
    2. Any superior stores are blended in from Context.
  2. what Freactal calls effects are actions
  3. the interpretation of actions are different:
    1. Returned value of actions are objects, not functions.
    2. Those objects are that are passed through ProviderComponent's setState, not state re-definers. i.e., all change is now in update mode by default.
    3. A lot more than effects are provided to actions; a whole context object is fed in with the current state, actions, and the store itself.
  4. There are optional reducer methods that are available to
    1. combine parent and current store's state and actions
    2. render any calculation/reduction of state properties into state.
  5. The Store class is available for use in any context.

How Freactal-Rebuild Works

Freactal defines a store, which is a blend of state and actions (effects in Freactal) that it expresses into React hierarchy. the store's actions change state, and Subscribers update as a response.

When you provide a state definition such as

const ViewBase = (({state, actions})) => (
  <div>
    <p>Foo = {state.foo}</p>
  <button onClick={() => actions.setFoo(4)} />
  </div>
)

const View = inject(ViewBase);


<Provider 
  initializer={() => ({foo: 0})}
  actions={({setFoo: (foo) => ({foo})})}
 >
    <View />
</Provider>

the provider will initialize its state to the value returned by the initializer and apply the results of its actions to that state, updating all children with that state.

Nested Providers' stores will decorate each other with the actions and state of their parents, allowing for a local state to handle tactical activitiy such as form management and still have access to the state and actions of parent stores.