Skip to main content

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

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.

Enjoyed "In JavaScript, there's a package for everything... and often for nothing."?

Follow me

Estéban Soubiran

Software engineer, conference speaker, and open source enthusiast.

Let's stay in touch

New articles, practical web development tips, and updates on my open source projects. Straight to your inbox.

Occasional emails about what I write and build.

Explore more talks

  1. Event: StrasbourgJS (opens in a new tab)StrasbourgDate:

    Discover the UnJS ecosystem

  2. Event: DevFest Dijon (opens in a new tab)DijonDate:

    Reactivity and signals: demystifying frontend magic

  3. Event: DevLille (opens in a new tab)LilleDate:

    Inside a pipeline: demystifying Vite and its plugins

What do you think?

Discussions

Loading discussions...

Add a comment

Checking your session...