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

@craigcollie/webpack-express-handler

v0.0.16

Published

### Overview This package aims to consolidate your development and production environments for handling static files and serving your `index.html`.

Downloads

14

Readme

Webpack express handler

Overview

This package aims to consolidate your development and production environments for handling static files and serving your index.html.

This means that your npm start script is used in both development, and production - and a single configuration can be used for both. This speeds up both development and testing time since your environments should be roughly identical.

Getting started

Installing the package into your project by running:

$ yarn add @craigcollie/webpack-express-handler

Required dependencies

This will install the core package, along with it's dependencies which require very little configuration. The dependencies will include:

Integrating into an express app

When creating your new express app, the webpack-express-handler will return your newly wrapped app with middleware applied, to cater for static file handling in both production and development environments.

const express = require('express');
const webpackExpressHandler = require('@craigcollie/webpack-express-handler');

const webpackConfig = require('./your/webpack/config');

const isProd = process.env.NODE_ENV === 'production';
const app = webpackExpressHandler(express(), isProd, webpackConfig);

app.get('/', (req, res) => {
  //  Your index.html is cached internally
  //  on the first request only
  res.send(app.locals.html);
});

app.listen(3000);

Running your server

As an example of how you might configure your server, the following could be added to your package.json.

{
  "scripts": {
    "start:dev": "node ./src/server.js",
    "start:prod": "NODE_ENV=production node ./src/server.js"
  }
}