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

prerender-ssg-webpack-plugin

v1.2.7

Published

A Webpack plugin for prerendering configured routes after Webpack has emitted all assets from a build compilation.

Downloads

36

Readme

Prerender SSG (Static Site Generation) Webpack Plugin

npm License: ISC

A Webpack plugin for prerendering configured routes after Webpack has emitted all assets from a build compilation.

Requirements: Node v14+ and Webpack v5+

About

After a successful production build, this plugin will:

  • spin up a Koa Server on the configured port (output.path by default),
  • create HTML content using Puppeteer's Headless Chromium Browser,
  • write HTML files to Webpack's output.path directory for each of the configured routes (['/'] by default),
  • & replace all files inside Webpack's output.path directory for which already exist.

Installation

npm i -D prerender-ssg-webpack-plugin

yarn add -D prerender-ssg-webpack-plugin

Usage

import PrerenderSsgWebpackPlugin from 'prerender-ssg-webpack-plugin';

const webpackConfig = {
    plugins: [
        /**
         * This is the most basic example.
         * Defaults will be used.
         * See "Details, Options & Defaults" for information on configuring this plugin.
         */
        new PrerenderSsgWebpackPlugin()
    ]
};

module.exports = webpackConfig;

Details, Options & Defaults (Optional)

/**
 * `PrerenderSsgWebpackPlugin`
 *
 * Prerenders one or more pages based on provided routes using Puppeteer.
 * This will only run for Webpack's production mode, otherwise it will abort.
 * @param options PrerenderSsgWebpackPluginOptions
 *
 * @example waitForSelector `waitFor: '#app'`
 *      This will wait for any selector to exist on the DOM before rendering occurs.
 * @example waitForFunction `waitFor: () => !!window.__APP_READY__`
 *      To manually trigger:
 *      @usage `window.__APP_READY__ = true;`
 * @example `waitForManual: true`
 *      When this is set, `waitFor` will be ignored. This expects a manual trigger of the prerender snapshot from the client code.
 *      This is great for waiting for async resolution & enrichment of content to the page before rendering occurs.
 *      To manually Trigger:
 *      @usage `if (window.__snapshot) window.__snapshot();`
 */

/**
 * `PrerenderSsgWebpackPluginOptions`
 *
 * These are the options which may be passed into `PrerenderSsgWebpackPlugin`.
 * All "options" are optional.
 * All defaults are set as values below, w/ allowable types in the comment following each option-key/value.
 */
const options: PrerenderSsgWebpackPluginOptions = {
    debug: false // boolean
    launchOptions: {
        args: ['--no-sandbox'],
        headless: true
    }, // puppeteer.LaunchOptions & puppeteer.BrowserLaunchArgumentOptions & puppeteer.BrowserConnectOptions & { product?: puppeteer.Product; extraPrefsFirefox?: Record<string, unknown>; }
    port: process.env.PORT || 8080, // number | string
    puppeteer: puppeteer, // PuppeteerNode
    routes: ['/'], // string[]
    setup: undefined, // (page: Page) => Promise<void>
    waitFor: undefined, // number | string | (() => boolean | Promise<boolean>)
    waitForManual: false, // boolean
    waitUntil: 'domcontentloaded' // 'domcontentloaded' | 'load' | 'networkidle0' | 'networkidle2'
};

Example Webpack Config

import HtmlWebpackPlugin from 'html-webpack-plugin';
import * as path from 'path';
import PrerenderSsgWebpackPlugin from 'prerender-ssg-webpack-plugin';
import puppeteer from 'puppeteer';
import { Configuration, ProgressPlugin } from 'webpack';

const template = require('./templates/index.js');
const isProd = process.env.NODE_ENV === 'production';

const webpackConfig: Configuration = {
    entry: './src/index.ts',
    mode: isProd ? 'production' : 'development',
    module: {
        // TS & Styles' configs not shown for brevity.
        rules: [tsRuleSet, stylesRuleSet]
    },
    output: {
        clean: true,
        filename: '[name].[contenthash].bundle.js',
        path: path.resolve(process.cwd(), 'build'),
        publicPath: '/'
    },
    plugins: [
        new ProgressPlugin(),
        new HtmlWebpackPlugin({
            templateContent: template,
            title: 'Super Cool Title'
        }),
        new CopyPlugin({
            patterns: ['./assets/**/*']
        }),
        new PrerenderSsgWebpackPlugin({
            port: 3000,
            // Uses `puppeteer` from "puppeteer-core" by default.
            puppeteer,
            routes: ['/', '/about', '/contact', '/shop/products'],
            setup: async (page) => {
                await page.evaluateOnNewDocument(() => {
                    (window as any).SOME_FLAG = true;
                });
            },
            waitForManual: true
        })
    ]
};

module.exports = webpackConfig;

Global Variables (in Browser Context)

  • window.__prerender will be set to true when this plugin is running.
  • window.__snapshot will be defined as a snapshot function only when the plugin option, waitForManual, is set to true.

Deployments

For CI/CD build pipelines, you will likely need to avoid downloading chromium if using the "puppeteer" package instead of "puppeteer-core". In this case, set the following environment variable: PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true.

ISC License (ISC)

Copyright (c) 2022 Claudio Nuñez Jr.

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.