Topic · 6 stories
6 stories tagged dependencies on AI Tamer, newest first.
A Rust crate that wraps a C library declares it with the links key, and Cargo allows only one package per links value in a build. Two major versions of such a crate cannot share one dependency graph.
Use npm ci in CI so builds install the committed dependency tree, and learn why it errors when package.json and package-lock.json disagree.
Cargo workspace.dependencies centralizes dependency declarations, but each member opts in through its own manifest. See how that keeps an AI application's crates honest about what they use.
Two crates in an agent CLI can request different features from the same dependency. Here is how Cargo combines those requests and how to trace them.
Cargo upgrades dependencies to versions it considers compatible, and a compatible update can still break you. What Cargo's version rules allow, what Cargo.lock protects, and where it doesn't reach.
npm's latest tag is whatever the publisher points it at, and Python's PEP 440 skips pre-releases by default. What each one installs when you ask for the newest.
