Skip to content
>devspeak
← glossary
level 1Understanding Your Project

Dependency

also: dependencies, deps

Outside code that your project relies on to work. If it's missing or broken, the parts of your app that use it break too.

a bit more technical

An external package, library or service a project needs in order to build or run. Code dependencies are usually listed with their versions in a file such as package.json or requirements.txt and installed by a package manager.

picture it

A bakery depends on its flour supplier. The bakery doesn't make flour, but if the supplier changes the recipe or stops delivering, the bread suffers.

why it matters

Agents add dependencies easily. Each one is code you didn't write, which can break, go out of date, or carry security problems. It's worth knowing when your agent adds one, and why.

what your agent might say
agent
I added one new dependency, date-fns, for formatting dates. It's small and widely used. Run npm install to pick it up.
how you might use it
you → your agent
Don't add any new dependencies for this. If you think one is truly needed, tell me which one and why before installing it.
common mistake

Thinking dependencies are part of your own code. Other people write and maintain them, and they change on their own schedule.

builds on