Resolve and Pin Project Dependencies
Resolves npm package specifiers to exact version strings and persists them into the project’s package.json. Inline exact versions are used as-is; ranges and bare names are resolved against the npm registry (cached in Redis). Pre-existing exact pins are never overwritten. Unknown packages and registry failures produce partial success — the affected specifiers are omitted from the response rather than failing the entire batch.
Authorizations
Use a JWT bearer token or a Veryfront API key in the Authorization header.
Path Parameters
Project slug, UUID, or domain
Body
npm package specifiers to resolve. Each entry may be a bare name, a name with an inline exact version, or a name with a semver range (e.g. "react", "[email protected]", "zod@^3", "@radix-ui/react-dialog").
1 - 100 elements1 - 200Preview branch name or ID whose package.json receives the resolved pins.
1 - 255"feature-a"
Package declarations observed by the caller. A null value means the package was absent. When supplied, every requested package must be present and stale declarations are not overwritten.
Response
Resolved pins (may be a partial set if some specifiers failed)
Resolved exact version pins keyed by package name. Includes both newly-written pins and pre-existing exact pins for all requested specifiers that were successfully resolved.
Whether the resolved pins were successfully written to the project's package.json. A false value means resolution succeeded but the write failed; pins still reflect the intended values and the caller may retry.
Requested packages not written because the current declaration no longer matched the caller snapshot.