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

parcel-react-ssr

v0.4.0

Published

Example of SSR with React and ParcelJS

Downloads

18

Readme

parcel-react-ssr

Simple example of how to do server-rendering. You will not believe how easy it is!

Using:

  • parcel-bundler
  • react
  • react-router-dom
  • react-helmet (SEO)

How to run

  • npm run dev - Run the development server with hot reload but no server-rendering
  • npm run build - Build for production, required before running
  • npm start - Start the production server

How does it work?

To do proper server-rendering, the code is bundled in two version: one for the browser and one for Node.js.

The browser version is in the dist/client folder and the Node.js version is in dist/server. However, they both share the same public path for their files: /dist and it points to the browser version. Go read the code, it's pretty straightforward!

Read the code!

  1. package.json - Start by reading the scripts section to understand how the build process works. Yes it's that dead simple!
  2. app/index.html - Your only HTML file acting as a template
  3. app/App.jsx - Your main application component shared between your browser and Node.js version
  4. app/HelloWorld.jsx - Dead simple hello world
  5. app/HelloWorld.scss - Example of SCSS
  6. server/index.js - Entry point for your Node.js version
  7. server/middleware.js - Middleware taking care of server-rendering
  8. server/generateHtml.js - Generate the HTML using index.html as the template with cheerio