There is all sorts of ways to keep an eye on it.
Bundlephobia will give you a look at the total size — both zipped and unzipped — along with download times, the number of required sub-dependencies it has, and whether or not it can be tree-shaked (tree-shook? tree-shaken?).
Speaking of “phobia,” there is also Package Phobia that shows the publish and install sizes of individual packages:
Your import and require statements can lett you know the size of that particular inclusion with the Import Cost extension.
The Webpack Bundle Analyzer does that.
Cost of modules is another analyzer, but it seems like it only looks at
package.json rather than the final bundle, then outputs it as a table:
Webpack Bundle Size Analyzer will show you a nested list of dependency weights, including the size of the bundle code itself, which is interesting:
package size has a simple CLI syntax for that:
You have another favorite way to keep your project in check?