Open the context
Choose the project folder and name the files or behavior involved.
Workflows
Coding workflows · Dependency lockfile drift
03
A concrete starting point
Compare direct dependency specifications in a manifest with the root entries of its lockfile. Report missing or changed specifications without rewriting the lockfile or running an installation.
Define the change
Describe the input, expected output and boundaries that must stay intact.
Inspect the work
Review the proposed edits and any commands before relying on their result.
Check the outcome
Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
Dependency lockfile drift
A concrete starting point
const root = lockfile.packages?.[""];
if (!root) return showDrift(["lockfile.root.missing"]);
const drift = [];
for (const group of ["dependencies", "devDependencies", "optionalDependencies"]) {
const wanted = manifest[group] ?? {};
const pinned = root[group] ?? {};
for (const name of new Set([...Object.keys(wanted), ...Object.keys(pinned)])) {
if (wanted[name] !== pinned[name]) drift.push(group + ":" + name);
}
}
return drift.length ? showDrift(drift) : reportAgreement();The example is a starting point for a real project, not a claim that generated code is already tested. Adjust paths, dependencies and expected behavior to match your application.