GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Comparing v5.6.6...v5.6.7 · jantimon/html-webpack-plugin

Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: jantimon/html-webpack-plugin
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading

Uh oh!

There was an error while loading. Please reload this page.

base: v5.6.6
Loading
Loading
...
head repository: jantimon/html-webpack-plugin
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading

Uh oh!

There was an error while loading. Please reload this page.

compare: v5.6.7
Loading
Loading
  • 3 commits
  • 6 files changed
  • 3 contributors

Commits on Apr 12, 2026

  1. refactor: remove lodash usage where possible (#1888)

    @gameroman
    gameroman authored Apr 12, 2026
    Configuration menu
    • View commit details
    • Copy full SHA for 0d1ff98
    • Browse repository at this point
    Copy the full SHA
    0d1ff98 View commit details
    Browse the repository at this point in the history

Commits on Apr 17, 2026

  1. fix: provide module/exports in VM sandbox for Node.js 25+ compatibili…

    …ty (#1889)
    
    Templates whose child compilation output is a CommonJS module (for
    example Rspack's HtmlWebpackPlugin child compilation, which wraps the
    evaluated template in `module.exports = ...`) were failing at evaluation
    time with `ReferenceError: module is not defined` under Node.js 25+.
    
    In 5.6.5 the VM context was switched away from a `...global` spread
    because spreading `global` on Node 25 throws once `localStorage` is
    touched without `--localstorage-file`. The replacement clone only
    exposes the standard globals plus `require`, so any CommonJS-wrapped
    source that assigned to `module.exports` hit the ReferenceError.
    
    Provide a throwaway `module = { exports: {} }` pair (plus `exports`
    aliasing it) in the sandbox so CommonJS-style outputs can evaluate
    without assuming the host Node version populates them.
    
    Refs: PR #1880, meta/docusaurus#11545
    @Marukome0743
    Marukome0743 authored Apr 17, 2026
    Configuration menu
    • View commit details
    • Copy full SHA for c862830
    • Browse repository at this point
    Copy the full SHA
    c862830 View commit details
    Browse the repository at this point in the history
  2. chore(release): 5.6.7

    @alexander-akait
    alexander-akait committed Apr 17, 2026
    Configuration menu
    • View commit details
    • Copy full SHA for fdef1b4
    • Browse repository at this point
    Copy the full SHA
    fdef1b4 View commit details
    Browse the repository at this point in the history
Loading

This comparison is taking too long to generate.

Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.

You can try running this command locally to see the comparison on your machine:
git diff v5.6.6...v5.6.7

Uh oh!

There was an error while loading. Please reload this page.

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.