Why the bundle contains duplicate dependencies

When multiple other dependencies and/or the application depend on a package, npm resolves the dependency tree and if a common version does not satisfy all the semver queries, it installs multiple instances of the same package. By installing multiple instances of the same dependency, npm meets the dependent package.json and avoids breaking existing functionality.

If the duplicate package is a front-end dependency, it is bundled multiple times. This increases the size of the bundle, negatively impacting the application's web performance and, in some cases, causing JavaScript runtime errors (ex: Duplicate React).

Resources:

• About semantic versioning
• semver

Example

Here's an example of how the bundle can contain duplicate dependencies. In an application that depends on @ant-design/icons@4.7.0 (resolved to v4.7.0) and antd@4.24.14, npm installs two different instances of @ant-design/icons because antd@4.24.14 depends on @ant-design/icons@^4.7.0 (resolved to v4.8.1):

{
  "name": "example-app",
  // ... package information
  "dependencies": {
    "@ant-design": "4.7.0",
    "antd": "4.24.14"
  }
}

npm list @ant-design/icons

example-fix-npm-dependencies@1.0.0 repo
├── @ant-design/icons@4.7.0
└─┬ antd@4.24.14
  └── @ant-design/icons@4.8.1

As a result, the bundle includes two versions of the same dependency:

How to identify duplicate dependencies

RelativeCI analyzes the bundle stats modules data, extracts the list of bundled dependencies, and identifies duplicate dependency instances. It presents the information as custom insights, metrics, and a list that you can filter and sort to discover the regressions quickly.

Duplicate packages insight

The duplicate packages insight shows the status and result of the duplicate packages analysis, allowing you to easily identify when there are regressions (new duplicate instances) or improvements (removed duplicates). The insight information is available on the bundle analysis report summary, job list, and all the integration summaries.

Duplicate packages metric

The number of duplicate packages is shown as a distinct metric on the report summary, the job list, and all the integration summaries.

You can also use the metric as a condition on the GitHub Commit Status Review or the Slack notification.

Duplicate packages data

To see the list of duplicate packages, go to the Packages section of the bundle analysis report and filter the results by the Duplicate filter. This will give you an overview of all the duplicate dependencies and their impact on the bundle size.

How to fix npm duplicate dependencies

The appropriate strategies for resolving npm duplicate dependencies may vary depending on your setup, dependencies, and versions. However, the following methods can help you eliminate duplicate packages, reduce bundle size, and enhance your application's web performance.

Run npm dedupe

npm dedupe can help quickly fix any existing issues in the package-lock.json file by flattening the dependency tree and regenerating the package-lock.json.

For example, the app dependency depends on @ant-design/icons@^4.6.0, and the correct semver resolution should be 4.8.1, though the package-lock.json resolves to 4.6.0:

npm explain @ant-design/icons

@ant-design/icons@4.6.0
node_modules/@ant-design/icons
  @ant-design/icons@"^4.6.0" from the root project

@ant-design/icons@4.8.1
node_modules/antd/node_modules/@ant-design/icons
  @ant-design/icons@"^4.7.0" from antd@4.24.14
  node_modules/antd
    antd@"^4.18.6" from the root projects

Running npm dedupe will correct the package-lock.json and remove the duplicate dependency:

npm dedupe
npm list @ant-design/icons
example-fix-npm-dependencies@1.0.0 repo
├── @ant-design/icons@4.8.1
└─┬ antd@4.24.14
  └── @ant-design/icons@4.8.1 deduped

• View example GitHub pull request
• View RelativeCI bundle analysis

Upgrade/downgrade to a common version

Another potential solution is to update and/or downgrade the dependency to a common version that the dependents can share. In the example above, we can update the application version to v4.8.1, the same as the version resolved for antd. npm will resolve both dependencies to v4.8.1.

npm install --save @ant-design/icons@^4.8.1
example-fix-npm-dependencies@1.0.0 repo
├── @ant-design/icons@4.8.1
└─┬ antd@4.24.14
  └── @ant-design/icons@4.8.1 deduped

• View example GitHub pull request
• View RelativeCI bundle analysis

Use npm overrides

The npm overrides configuration allows you to explicitly set package versions and override the npm resolution for any dependency, direct or transitive. In our example, we can override the resolved version of @ant-design/icons to 4.7.0.

Again, updating a package version, especially a major version, can break existing functionality. Remember to follow the change log of the dependency for changes, and ensure you test after updating.

{
  "name": "app",
  /* ... */
  "dependencies": {
    "@ant-design/icons": "^4.6.0",
    "antd": "^4.18.6",
    /* ... */
  },
  "overrides": {
    "antd": {
      "@ant-design/icons": "4.7.0"
    }
  }
}

npm list @ant-design/icons

example-fix-npm-dependencies@1.0.0
├── @ant-design/icons@4.7.0
└─┬ antd@4.24.14
  └── @ant-design/icons@4.7.0 deduped

• View example GitHub pull request
• View RelativeCI bundle analysis

Use webpack configuration

Webpack allows dependency imports to be overridden at bundle time using the resolve.alias configuration option.

Don't forget that updating a package version, especially a major version, can break existing functionality. Always follow the change log of the dependency for changes and test after the update.

To point all the app imports of @ant-design/icons to the same version, we can add an entry to resolve.alias:

module.exports = {
  // ... webpack config
  resolve: {
    alias: {
      '@ant-design/icons': path.join(
        __dirname,
        'node_modules/@ant-design/icons',
      ),
    }
  }
};

• View example GitHub pull request
• View RelativeCI bundle analysis