Gathering detailed insights and metrics for clam-duplicate-package-checker-webpack-plugin
Gathering detailed insights and metrics for clam-duplicate-package-checker-webpack-plugin
🕵️ Webpack plugin that warns you when a build contains multiple versions of the same package
Installations
npm install clam-duplicate-package-checker-webpack-pluginDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
12.18.3
NPM Version
6.14.6
Releases
Unable to fetch releases
Languages
1
JavaScript
JavaScript (100%)
Developer
kingback
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
52 Commits
1 Watchers
5 Branches
1 Contributors
Updated on Jul 03, 2020
Maintainers
1
Package Meta Information
Latest Version
3.1.0
Package Id
clam-duplicate-package-checker-webpack-plugin@3.1.0
Unpacked Size
21.91 kB
Size
6.24 kB
File Count
8
NPM Version
6.14.6
Node Version
12.18.3
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
clam-duplicate-package-checker-webpack-plugin
Webpack plugin that warns when your bundle contains multiple versions of the same package.
Why?
It might be possible that a single package gets included multiple times in a Webpack bundle due to different package versions. This situation may happen without any warning, resulting in extra bloat in your bundle and may lead to hard-to-find bugs.
This plugin will warn you of such cases to minimize bundle size and avoid bugs caused by unintended duplicate packages.
Motivation: https://github.com/webpack/webpack/issues/385 and https://github.com/webpack/webpack/issues/646.
Install
1npm install clam-duplicate-package-checker-webpack-plugin --save-dev
Configuration
Add the plugin to your webpack config:
1var DuplicatePackageCheckerPlugin = require("clam-duplicate-package-checker-webpack-plugin"); 2 3module.exports = { 4 plugins: [new DuplicatePackageCheckerPlugin()] 5};
You can also pass an object with configurable options:
1new DuplicatePackageCheckerPlugin({ 2 // Also show module that is requiring each duplicate package (default: false) 3 verbose: true, 4 // Emit errors instead of warnings (default: false) 5 emitError: true, 6 // Show help message if duplicate packages are found (default: true) 7 showHelp: false, 8 // Warn also if major versions differ (default: true) 9 strict: false, 10 // output duplicate-packages.json (default: false) 11 // or { path: path.join(process.cwd(), 'build'), filename: 'my-packages.json' } 12 output: true, 13 /** 14 * Exclude instances of packages from the results. 15 * If all instances of a package are excluded, or all instances except one, 16 * then the package is no longer considered duplicated and won't be emitted as a warning/error. 17 * @param {Object} instance 18 * @param {string} instance.name The name of the package 19 * @param {string} instance.version The version of the package 20 * @param {string} instance.path Absolute path to the package 21 * @param {?string} instance.issuer Absolute path to the module that requested the package 22 * @returns {boolean} true to exclude the instance, false otherwise 23 */ 24 exclude(instance) { 25 return instance.name === "fbjs"; 26 } 27});
Strict mode
Strict mode warns when multiple packages with different major versions (such as v1.0.0 vs v2.0.0) exist in the bundle.
Packages with different major versions introduce backward incompatible changes and require either interventions on third-party packages or unsafe workarounds (such as resolving differing package major versions dependencies with a single version).
It is suggested that strict mode is kept enabled since this improves visibility into your bundle and can help in solving and identifying potential issues.
Resolving duplicate packages in your bundle
There are multiple ways you can go about resolving duplicate packages in your bundle, the right solution mostly depends on what tools you're using and on each particular case.
Webpack resolve.alias
Add an entry in resolve.alias which will configure Webpack to route any package references to a single specified path.
For example, if Lodash is duplicated in your bundle, the following configuration would render all Lodash imports to always refer to the Lodash instance found at ./node_modules/lodash.
alias: {
lodash: path.resolve(__dirname, 'node_modules/lodash'),
}
Note: Aliasing packages with different major versions may break your app. Use only if you're sure that all required versions are compatible, at least in the context of your app
Yarn install --flat
Yarn allows flat installations (yarn install --flat) which will only allow one version of each package to be installed.
Yarn resolutions
If you want more control over your overridden dependency versions and don't feel like using yarn install --flat, yarn supports "selective version resolution" which allows you to enforce specific versions for each dependency.
package.json
{
"dependencies": {
"lodash": "4.17.0",
"old-package-with-old-lodash": "*"
},
"resolutions": {
"old-package-with-old-lodash/lodash": "4.17.0"
}
}
NPM Dedupe
If you use NPM and not Yarn, you can try running npm dedupe. NPM may leave multiple versions of the same package installed even if a single version satisfies each semver of all of its dependants.
Bump your dependencies
If your project is using an old version of a package and a dependency is using a newer version of that package, consider upgrading your project to use the newer version.
File issues!
If your project has a dependency and it's using an outdated version of a package, file an issue and notify the author to update the dependencies. Let's help keep our projects green and our applications secure, performant and bug-free!
Webpack versions
Webpack 3.x
npm install clam-duplicate-package-checker-webpack-plugin@^2.1.0 --save-dev
Webpack 4.x
npm install clam-duplicate-package-checker-webpack-plugin
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Score
3
/10
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More