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 🙏

© 2025 – Pkg Stats / Ryan Hefner

wildcard-server-webpack-plugin

v1.0.7

Published

Generates a server which serves index.html to all routes so you can focus on just your front end code.

Readme

wildcard-server-webpack-plugin

Generates an express server which serves index.html to all routes so you can focus on just your front end code.

Problem

When using client-side routing solutions for single page applications (e.g. react-router), users cannot refresh the page. It is necessary to provide a server.js file which redirects all requests back to /index.html.

One solution is to put this server.js in your output folder; however, this means you to check in that folder into source control.

Another solution is to put your server.js in your src/ folder and use a webpack plugin to move it to dist/ once your build is done; however, this means your project contains both front-end and back-end code.

Solution

The purpose of this plugin is to generate a server.js file in the output folder of your webpack project when your project compiles. This means you don't need to check in your output folder to source control. You also don't need to muddy your client-side code with server-side code.

Usage

Use this with your production webpack.config file. You can still use webpack-dev-server for local development. See the webpack docs for tips on how to have separate dev and prod webpack configs.

const WildcardServerPlugin = require('wildcard-server-webpack-plugin');

...

plugins: [
        ...
        new WildcardServerPlugin()
    ]

Run the server with node dist/server.js. You can set up a script in your package.json to do this - `"start": "node dist/server.js"

I recommend using this alongside html-webpack-plugin. With both of these plugins combined, you can stick to React.