AES Encryption Explained: How It Works and Why It Matters
Jun 23, 2026
Paste your package.json to analyze dependencies — count, categories, version ranges, license types, and bundle size estimates.
Total Dependencies
0
Production
0
Dev Only
0
Estimated Size
0 MB
| Package | Version | Type | Category |
|---|
This tool analyzes your package.json file and provides insights into your project's dependency tree. It categorizes packages by type (production vs dev), analyzes version range patterns, estimates bundle size contribution, and groups dependencies by category (framework, utility, testing, build tools, etc.).
Understanding your dependencies helps you identify unused packages, detect outdated version patterns, and make informed decisions about bundle size optimization. All analysis happens in your browser — no data is uploaded to any server.
package.json file and copy the entire contents to your clipboard.The tool estimates bundle size based on average package sizes for common npm categories. Production dependencies are estimated at ~50KB each, dev dependencies at ~10KB each. These are rough estimates — actual sizes depend on the specific packages and your bundler configuration.
Dependencies are categorized by matching package names against common patterns for frameworks (react, vue, angular), testing (jest, mocha, cypress), build tools (webpack, vite, esbuild), utilities (lodash, axios, dayjs), and more. Unknown packages are grouped as "Other."
The version range analysis shows how your dependencies specify their versions — exact pinning, caret (^), tilde (~), or ranges. Caret ranges (^) allow minor/patch updates and are considered best practice. Excessive exact pinning may indicate outdated dependencies that are harder to update.
No. Semua proses terjadi di browser Anda. Data tidak pernah dikirim ke server.
Blog
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026