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

red-ux

v1.0.2

Published

performance utilities for progressive web apps

Downloads

110

Readme

red-ux

performance utilities for progressive web apps.

take your user experience out of the red

npm version coverage Build



React: Reduce unneeded re-rendering with shouldUpdate

import React, {Component} from 'react';
import { shouldUpdate } from 'red-ux'

export class List extends Component {

  shouldComponentUpdate(nextProps, nextState){
    return shouldUpdate(nextProps, nextState);
  }

  render() {
    return (
      <ul>{
        this.props.data.map(({name,id}) => <li key={id}>{name}</li>)
      }</ul>)
    }
}

Redux: Result caching with genSelectState

genSelectState uses Reselect under the hood.

This function will let you wrap computationally expensive logic.

Example; using React & Redux.

  • Without genSelectState
import React, {Component} from 'react';
import { connect } from 'react-redux';

export class List extends Component {

  render() {

    const posts = this.props.posts.map( post => ({ id: post.uid, name:post.userName }) )

    return (
      <ul><li>{this.props.user.name} List</li>{
        posts.map(post => <li key={post.id}>{post.name}</li>)
      }</ul>)
    }
}

const map_state_to_props = (state)=>({
  user  : state.user,
  posts : state.posts
}}

export default connect(map_state_to_props)(List);
  • With genSelectState
import React, {Component} from 'react';
import { connect } from 'react-redux';
import { genSelectState } from 'red-ux'

export class List extends Component {

  render() {

    return (
      <ul><li>{this.props.user.name} List</li>{
        this.props.posts.map(post => <li key={post.id}>{post.name}</li>)
      }</ul>)
    }
}

const map_state_to_props = (state)=>({
  user  : state.user,
  posts : state.posts
}}

const works = {
  posts : posts => posts.map( post => ({ id: post.uid, name:post.userName }))
}

export default connect(genSelectState( map_state_to_props, works ))(List);

Now the transformation will only happen once on each if the reference passed in was the same. This means that the posts transformation will happen on the first call and will return the same calculated value is the posts have not changed.

An alternative api is available that more closely follows reselect

import React, {Component} from 'react';
import { connect } from 'react-redux';
import { genSelectState } from 'red-ux'

export class List extends Component {

  render() {

    return (
      <ul><li>{this.props.user.name} List</li>{
        this.props.posts.map(post => <li key={post.id}>{post.name}</li>)
      }</ul>)
    }
}

const selecters = {
  user  : state => state.user
  posts : state => state.posts
}

const works = {
  posts : posts => posts.map( post => ({ id: post.uid, name:post.userName }))
}

export default connect(genSelectState( selecter, works ))(List);

You pass an Object as the first argument to genSelectState that maps the to select functions

  • If you have multiple pieces of state. Pass an Array
const map_state_to_props = (state)=>({
  user  : state.user,
  posts : [state.posts.a,
           state.posts.b]
}}
const works = {
  posts : (a,b) => posts.map( post => ({ id: post.uid, name:post.userName }))
}

and

const selecters = {
  user  : state => state.user
  posts : [state => state.posts.a,
           state => state.posts.b]
}

const works = {
  posts : (a,b) => posts.map( post => ({ id: post.uid, name:post.userName }))
}

📌 Note: As an optimization. The works object will has it's properties wrapped. So feel free to call works properties after the fact, knowing your getting optimized results.

const works = {
  foo : (a) => stuff(a),
  bar : (a,b) => works.foo(a) + b,
  cat : (a,b) => works.bar(a,b) + 1000,
}

works.bar will only be executed once, even though its referenced twice.