Version History

(2)

📦 webpack2

A full version history of the webpack2 package with size, number of distributed files and dependency evolution.

Unpacked Size

Historyical package size changes accross diffent versions of the package

Number of Files

Historycal changes package file numbers across different versions of the package

Dependencies

Number of dependencies for all the versions of the package

Versions Summary

Webpack2, a powerful module bundler, saw two closely released versions, 3.11.0 and 3.11.1, both aiming to streamline the process of packaging JavaScript modules for browser deployment. Both versions share the same core functionality as described in their shared description of packing CommonJs/AMD modules, enabling code splitting for on-demand loading, and supporting loaders for diverse file types (JSON, JSX, CSS, etc.).

Both webpack2 versions have effectively the exact same dependencies, including acorn, ajv, async, enhanced-resolve, and webpack-sources, providing the necessary tools for module parsing, validation, and resolution. The "devDependencies" also match, a list full of tools necessary for the developer and quality assurance like eslint, mocha, react, and loaders for specific frameworks.

The key difference between versions 3.11.0 and 3.11.1 lies in their release dates. Version 3.11.0 was released on May 14th, 2018, at 02:38:49 UTC, while version 3.11.1 followed shortly after, on the same day at 03:46:53 UTC. It's also worth noting there is a single byte difference betweem the unpacked sizes of the two versions. The minimal time difference between releases suggests a bug fix in 3.11.1 was needed shortly after releasing 3.11.0.

Version	Dependencies	Dev Dependencies	Peer Dependencies	Distributed Files	Unpacked Size	Details
3.11.1	22	39	0	282
3.11.0	22	39	0	282

Page 1 of 1

Version	Deps	N. of Files	Size
3.11.1	61	282
3.11.0	61	282

Page 1 of 1

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.