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

react-redux-universal-render

v0.0.4

Published

A somewhat opinionated way to set up a React app for full-page universal rendering.

Downloads

2

Readme

react-redux-universal-render

WARNING: This is first-draft technology. It does not yet include proper tests. Use at your own risk or help contribute.

A somewhat opinionated way to set up a React app. It uses:

  • react, duh.
  • redux for state.
  • react-redux to bridge the two.
  • react-helmet for <head> management.

And it provides a simple setup function for rendering a full page string from the server and then inflating it on the browser client.

Setup

Define how the output will be constructed from the view name and data. Export a module to be shared between the client and server bundles. The setup function takes two options: getView and createReduxStore.

import React from 'react'
import {createStore} from 'redux'
import setup from 'react-redux-universal-render'

// Define how view names will be mapped to React components
const VIEWS = {
  'home/index': (props) => <h1>{props.greeting}</h1>
}
function getView(name) {
  return VIEWS[name]
}

// Define your redux reducer.
function reducer(state, action) {
  return state
}

// Define how your redux store will be initialized from view data.
function createReduxStore(props) {
  // The simplest choice is to set the initial state of the store to the exact
  // props that were sent to the render function.
  return createStore(reducer, props)
}

// Create and export the render function to be used by both the client and server.
const createRenderer = setup({
  getView,
  createReduxStore,
})
export default createRenderer

react-helmet

Read the react-helmet docs for client-side usage. The renderer we just created will handle the server-side Helmet.rewind and <head> construction for you automatically.

Server Usage

Import your setup module. Initialize a render function with the server-side react-dom object. Call your render function with the view name and data. It will return an HTML string.

import ReactDOMServer from 'react-dom/server'
import createRenderer from './my-render-setup'

const render = createRenderer(ReactDOMServer)

const htmlString = render('home/index', {greeting: 'Hello, World!'})

Client Usage

Import your setup module. Initialize a render function with the client-side react-dom object. The render function does not use any arguments. It will reuse the view name and data from the server to inflate the react components. All you need to do is make sure the DOM is ready.

import ReactDOM from 'react-dom'
import createRenderer from './my-render-setup'

const render = createRenderer(ReactDOM)

window.addEventListener('DOMContentLoaded', render)

Recipes

Express

import http from 'http'
import express from 'express'
import ReactDOMServer from 'react-dom/server'
import createRenderer from './my-render-setup'

// Define middleware
const render = createRenderer(ReactDOMServer)
const renderMiddleware = function(req, res, next) {
  res.render = (...args) => res.send(render(...args))
  next()
}

// Create express app with middleware
const app = express()
app.use(renderMiddleware)
app.get('/', (req, res) => res.render('home/index', {greeting: 'Hello, World!'}))

// Start server
http.createServer(app).listen(process.env.PORT || 3000)