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

iniquest

v0.0.5

Published

A lightweight library to help with async data fetching before rendering with react-router.

Downloads

11

Readme

iniquest

A lightweight (~30 LOC) library to help with async data fetching before rendering with react-router.

Installation

$ npm i iniquest -S

Usage

Below is an example of how you could use iniquest with express. For a more detailed example, that also demonstrates acting on POST-requests, check out maximilianschmitt/full-stack-react.

server.js

const routes = (
  <Route handler={App}>
    <Route name="home" path="/" handler={Home} />
    <Route name="ip" path="/ip" handler={Ip} />
  </Route>
);

app.use(function(req, res, next) {
  Router.run(routes, req.path, function(Handler, state) {
    iniquest
      .run(state, req).then(initialState => {
        res.send(React.renderToString(<Handler initialState={initialState} />));
      })
      .catch(next);
  });
});

app-component.js

Here, RouteHandler will be the Ip component below if the user navigates to /ip.

class App extends React.Component {
  render() {
    return (
      <div className="app">
        <RouteHandler initialState={this.initialChildState()} />
      </div>
    );
  }
}

mixin.onClass(App, iniquest.InitialChildState);

ip-component.js

class Ip extends React.Component {
  render() {
    return <div>Your ip is: {this.state.ip}</div>;
  }
}

mixin.onClass(Ip, iniquest.InitialStateFromProps);

// implement prepareForRequest on a RouteHandler
// to make an async request before rendering
Ip.prepareForRequest = function(req) {
  return fetch('http://ip.jsontest.com').then(res => res.data);
};

Todo

  1. Add ability for parent RouteHandlers to pass params to the prepareForRequest of a child RouteHandler, maybe like this:

    Component.prepareChildForRequest(initialState, childRoute) : opts
    Component.prepareForRequest(req, opts) : initialState
  2. Find a simple solution so that (1) can optionally run prepareForRequest-calls in parallel if opts for the child's preparation are not dependent on the parent's prepareForRequest