Webpack.
Webpack is a module bundler that resolves an application's dependency graph and emits optimised assets. It is configured explicitly rather than by convention, which makes it capable of almost any build requirement and makes an inherited configuration one of the harder artefacts to take ownership of.
Where Webpack fits on a long engagement.
Most Webpack work is archaeology. A configuration assembled over several years by people who have left, carrying loaders for file types the application no longer uses and plugins whose purpose is undocumented. The first useful task is rarely optimisation; it is establishing what the config actually does, because nobody currently on the project can say with confidence.
Webpack remains the right answer more often than its reputation suggests. Module federation for genuinely independent deployable frontends, unusual asset pipelines, and long-lived enterprise builds with specific requirements are all cases where explicit configuration beats convention. The question is whether the complexity is earned or merely inherited.
What an assigned team does with Webpack.
Build configuration is the clearest example of knowledge that lives in a person rather than a document. On a standing assignment that knowledge accumulates and gets written down; on rotating capacity it is rediscovered from scratch every time, which is why build changes take days on some teams and an afternoon on others.
The realistic decision is usually migrate or document, and it depends on whether the configuration earns its complexity. Either way it is planned work with a defined outcome, which is how scope is set on a dedicated software development team rather than raised as an emergency when a build breaks.
What we use Webpack for.
- Inheriting a build with no maintainer Documenting and simplifying a configuration to the point where a change is routine rather than risky.
- Module federation across independent frontends Separately deployed applications sharing runtime dependencies, where the explicit configuration is the feature.
- A migration decision made on evidence Establishing whether the config's complexity is required or merely historical, before committing to move.
How Webpack capacity is assigned.
Webpack work sits inside frontend capacity under software development outsourcing, with build ownership treated as a deliverable rather than an assumed side effect.
Tell us what your roadmap needs Webpack for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.