Question 1

How to use package-size with a local file or folder?

Accepted Answer

Use relative paths like `package-size ./dist/index.js` or the `--cwd` flag to analyze packages in the current directory, as shown in the usage examples for local file support.

Question 2

package-size vs bundlephobia: which is better for checking npm package sizes?

Accepted Answer

package-size offers more accurate results by actually bundling with Webpack, while bundlephobia provides faster estimates. Use package-size for precise analysis in Webpack-based projects, and bundlephobia for quick checks.

Question 3

How to exclude certain dependencies in package-size analysis?

Accepted Answer

Use the `--externals` flag to specify packages to exclude, such as `package-size styled-jsx/style --externals react`, which simulates real-world usage by leaving those dependencies unbundled.

Question 4

Can package-size be integrated into a CI/CD pipeline?

Accepted Answer

Yes, use the CLI with `--output` to save results in JSON format or the Node.js API to programmatically fetch sizes, making it easy to automate bundle size tracking in continuous integration.

Question 5

Does package-size work with Yarn 2 or pnpm?

Accepted Answer

The README doesn't explicitly support alternative package managers, mentioning only yarn or npm, so it might have limited functionality or require additional configuration for Yarn 2 or pnpm.

Question 6

How to analyze multiple versions of a package with package-size?

Accepted Answer

Specify versions in the CLI command, like `package-size react@0.10 react@0.14 react@15`, to compare bundle sizes across different releases, as highlighted in the multi-version analysis feature.

package-size

What is package-size?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions