February 3, 2011
Browserify first released
James Halliday published Browserify on February 3, 2011 — a bundler that let browsers use NodeNode.js — JavaScript on the server via an event-driven runtime built on V8.-style `require()` for npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. modules.
What it was for
Browserify walks `require()` dependencies and packs them into one file for the browser — the first mainstream way to compose npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. packages on the client. It paved the way for webpack, RollupA JavaScript module bundler — tree-shaking and efficient production builds for libraries., and the modern frontend toolchain. Example: `browserify main.js -o bundle.js` ships lodash and your app code to static hosting.
Why it's here
Browserify proved npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. modules could run in browsers, not just on servers.
Why it mattered
It launched the module-bundler era that reshaped how JavaScript apps are built and deployed.
What it solved
Browsers had no native module system; developers could not reuse the growing npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. ecosystem client-side.
Related
- npm first releasedJanuary 12, 2010
- Node.js first releasedMay 27, 2009
- webpack first releasedMarch 10, 2012
- Rollup first releasedMay 21, 2015