# In JavaScript, there's a package for everything... and often for nothing.

> Examine the cost of unnecessary JavaScript dependencies and learn how to reduce the footprint of packages, bundles, and the delivery pipeline.

- Date: 2025-06-26
- Event: [BreizhCamp](<https://breizhcamp.org/>)
- Location: Rennes, France
- Topics: bundle-size, dependencies, e18e, javascript, package-management, performance

## Resources

- [Article](<https://talks.soubiran.dev/2025-06-26/breizhcamp/article>)
- [Slides](<https://talks.soubiran.dev/2025-06-26/breizhcamp>)
- [PDF](<https://talks.soubiran.dev/2025-06-26/breizhcamp/pdf>)
- [Source code](<https://talks.soubiran.dev/2025-06-26/breizhcamp/src>)

## Summary

JavaScript projects often depend on packages that developers never install directly. Using `is-string` as an example, this talk examines transitive dependencies and the contents of `node_modules`, where metadata and small utilities can account for much of what gets downloaded.

It introduces `node-modules.dev`, `pkg-size`, `deptree`, and `npmgraph`, then presents e18e, or Ecosystem Performance, and its focus on cleaning up, speeding up, and improving the JavaScript ecosystem.