Update CLI & TurboSnap docs to reflect we now trace dependencies

[ghengeveld]

Merge after we ship Enhanced TurboSnap.

[linear]

AP-2273 Finer-grained full rebuilds from lockfiles

Currently when using TurboSnap, a change to a package.json or yarn.lock/package-lock.json/etc results in a full retest of all stories in a project. However, in a monorepo setup, there may be multiple packages, each with their own package.json . If an unrelated package (e.g. a server-only package) adds/removes/updates a dependency, it would cause a retest of all projects in the monorepo. This can be gotten around by using the --untraced flag (like --untraced \"./packages/!(foo)/**\" to only retest when files in the foo package change), but it's not ideal to have to specify these. Furthermore, it means that non-dependency changes to a package.json file (like adding an NPM script) automatically trigger retests, though the file changes may be unrelated to any components.

Instead, we could look within the package manager's lockfile to see what dependencies changed, and if any of those are imported by components in a given package, we'd mark those components recursively as needing to be retested. See additional details here.

• Reach out to Olivia from Brex ([email protected]) once this is released

[netlify]

👷 Deploy request for chromatic-docs pending review.

A Netlify team Owner will need to approve the deploy before you can run your build.

Are you a team Owner? Visit the deploys page to approve it →

Need more help? Learn more in the Netlify docs →

Name	Link
🔨 Latest commit	2848ead

[jonniebigodes]

Thanks for this @ghengeveld. I'll take a deeper look tomorrow morning my time and if nothing requires changes, I'll merge it.

[jonniebigodes]

With the latest commit, I polished up the document for clarity and some minor grammar issues spread across the document. Merging this