macOS
brew install webpacklocal Homebrew formula metadata
brew
webpack のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。
インストール
brew install webpacklocal Homebrew formula metadata
sudo apt install webpackDebian stable package indexes · webpack · ソース: deb.debian.org
nix profile install nixpkgs#webpack-clinixpkgs package indexes · pkgs/by-name/we/webpack-cli/package.nix · ソース: api.github.com
概要
Bundler for JavaScript and friends
履歴
webpack is a JavaScript module bundler that builds a dependency graph from application entry points and emits static assets for browsers and other targets. It became one of the defining tools of the 2010s front-end build era because it treated JavaScript, CSS, images, and other assets as modules connected by loaders and plugins.
The public `webpack/webpack` repository was created on March 10, 2012. GitHub's ReadME Project recounts that Tobias Koppers created webpack while working on a master's thesis for web applications, beginning as an optimizer born from practical need and growing through collaboration with users.
webpack's core model is a static dependency graph. The official concepts documentation explains that webpack starts from one or more entry points, follows the modules an application needs, and combines them into bundles. That model fit the rise of CommonJS, AMD, ES modules, transpilation, CSS preprocessors, and single-page applications.
webpack 4, released in February 2018, lowered the barrier for common use by making a configuration file optional for simple bundles while preserving deep configurability. webpack 5 followed on October 10, 2020, with a major release focused on long-term caching, removals of deprecated behavior, new web-platform features, and development-experience improvements.
webpack spread because it solved several front-end problems at once: bundling JavaScript for browsers, code splitting for on-demand loading, asset processing through loaders, optimization through plugins, and a configurable build pipeline that frameworks could wrap. The ReadME Project characterized it as used by millions of developers around the world.
Its adoption was reinforced by the surrounding loader/plugin ecosystem and by framework tooling that hid or generated webpack configurations. Even as newer tools such as Rollup, Parcel, esbuild, Vite, and Turbopack changed developer expectations, webpack remained significant in long-lived applications, enterprise build systems, and projects relying on its mature plugin surface.
webpack 5's Module Federation gave the project a second adoption story beyond classic bundling. The webpack 5 release notes describe Module Federation as allowing multiple webpack builds to work together at runtime, enabling independently built code to behave like a connected module graph.
Developers use webpack by defining entry points, output settings, loaders, plugins, and mode-specific behavior, usually in `webpack.config.js` for non-trivial projects. Since webpack 4, simple projects can run without an explicit config, but package maintainers still recognize the config file as the center of serious webpack setups.
Common usage patterns include compiling modern JavaScript and TypeScript for browsers, bundling CSS and images with content hashes, splitting code by route, running development servers with hot updates, and generating optimized production assets. In larger systems, webpack configuration often becomes shared infrastructure owned by platform or build-tooling teams.
webpack is package-nerd famous because it made `node_modules` and browser delivery collide at industrial scale. Its loader and plugin conventions shaped how npm packages advertise browser entry points, side effects, CSS handling, and asset behavior.
It is also a landmark in build-tool ergonomics: powerful enough to become the default, configurable enough to become notorious, and stable enough that newer tools are often explained by comparing what they simplify or replace from webpack-era workflows.
セキュリティ状態
webpack に一致するローカルシークレット処理マニフェストは見つかりませんでした。将来の対応で安定したパッケージ URL を使えるよう、Nucleus パッケージメタデータはここに公開されています。
エージェントに無人実行させる前に、このツールが平文の認証情報を読むか、リモート状態を書き込むか、成果物を公開するか、プラグインを起動するかを確認してください。
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
webpack.config.js実行可能ファイル
| コマンド | 種類 | 公開範囲 | メモ |
|---|---|---|---|
webpack | cli | グローバル実行可能ファイル | |
webpack-cli | cli | グローバル実行可能ファイル |
鮮度
これらの信号は、ページ生成時期、パッケージマネージャの活動、上流リリース比較を分けて示します。バージョン遅れは、証拠 URL と比較可能なバージョンがある場合だけ警告されます。
インストールメタデータ
| パッケージキー | brew:webpack |
|---|---|
| バージョン | 5.109.0 |
| パッケージマネージャ | Homebrew |
| パッケージマネージャページ | https://formulae.brew.sh/formula/webpack |
| ホームページ | https://webpack.js.org/ |
| リポジトリ | https://github.com/webpack/webpack |
| 上流ドキュメント | https://webpack.js.org/concepts |
| ライセンス | MIT |
| ソースアーカイブ | https://registry.npmjs.org/webpack/-/webpack-5.109.0.tgz |
| 最終更新 | 2026-07-24T22:00:09Z |
| Pulse | updated |
| 依存関係 | node |
| Bottle | 利用可能 (対象 all) |
| Homebrew post-install | 未定義 |
| サービス | 宣言なし |
レジストリ情報
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | webpack |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
ソースデータベース一致
一致は外部パッケージマネージャインデックスから取得され、ローカルの Automic Vault パッケージリンクとは分けて表示されます。
webpack 5.97.1+dfsg1+~cs11.18.27-3
Packs CommonJs/AMD modules for the browser
https://github.com/webpack/webpack
sudo apt install webpackwebpack 5.76.1+dfsg1+~cs17.16.16-1
Packs CommonJs/AMD modules for the browser
https://github.com/webpack/webpack
sudo apt install webpackwebpack-cli
nix profile install nixpkgs#webpack-cliソース経路
このページは scripts/generate-pkg-sqlite.py が生成した非公開のパッケージ SQLite アーティファクトから av-web によって提供されます。
View the package source record on GitHub.