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

fluxible-resolver

v3.1.19

Published

Takes an object of resolvers, keyed by the name of the prop they are resolving, and doesn't render the underlying component until all data is available.

Downloads

62

Readme

fluxible-resolver

fluxible-resolver is built on top of react-resolver and connectToStores, allowing you to fetch prop values asynchronously before rendering your component, using fluxible actions and stores. In addition, you can declare dependencies on other resolvers so you can assume they are available when resolving your depenent prop.

You can think of fluxible-resolve like a CDN. When a request comes in first we check if we already have the content stored in our cache. If so, great, return the content. If not, fetch it from the original source. In this case, the incoming request is React rendering your component, the cache is getStateFromStores + isResolved, and the http client that fetches from the original source is resolver.

resolveToStores

Takes an object of resolvers, keyed by the name of the prop they are resolving, and doesn't render the underlying component until all data is available.

resolver fields
  • dependencies Array<String>: optional array of strings, naming either props (must be specified via propTypes) or other resolvers.
  • getStateFromStores (FluxibleContext, Array<any>): any: required function that takes context and dependency values and returns the current value for the prop.
  • isResolved (any, Array<any>): boolean: optional function which takes the current value and the dependency values and returns whether the prop value is available.
  • resolver (FluxibleContext, Array<any>): Promise: required fluxible action that takes the arry of dependency values as the payload and fetches the value.
  • stores Array<FluxibleStore | String>: required array of fluxible stores, or store names.
import { resolveToStores } from 'fluxible-resolver';

const resolvers = {
    propName: {
        dependencies: [], // optional
        getStateFromStores: (context, dependencyValues) => context.getStore(PropStore).getValue(),
        isResolved: (currentValue, dependencyValues) => !!currentValue, // optional - by default checks if currentValue is defined
        resolver: (context, dependencyValues) => context.executeAction(fetchPropValue),
        stores: [PropStore] // getStateFromStores can only call context.getStore for stores listed here
    }
};

/**
 * propTypes are optional, but are required if you want a resolver to depend
 * on a prop passed to the container rather than depending on another resolver
 **/
const propTypes = {

};

const Container = resolveToStores(resolvers, propTypes)(Component);