Resolve project dependencies - Veryfront

resolveProjectDependencies(input: ResolveProjectDependenciesInput!): ResolveProjectDependenciesPayload!

Existing exact pins remain unchanged. Registry failures give partial success; stale snapshot declarations are skipped. Requires project.files.write.

Arguments

Argument	Type	Required
`input`	`ResolveProjectDependenciesInput!`	Yes

Input fields

input

ResolveProjectDependenciesInput

Field	Type	Required	Description
`projectReference`	`String!`	Yes	Project UUID or slug.
`branch`	`String`	No	Branch name or UUID, 1-255 characters without surrounding whitespace. Omit for main.
`specifiers`	`[String!]!`	Yes	1-100 npm specifiers, each 1-200 characters: bare package, exact version or semver range.
`expectedDeclarations`	`JSONObject`	No	Observed package declarations, at most 100 entries with string values up to 200 characters. Each requested package must be present; null means absent. Changed declarations are skipped.

Response

Returns ResolveProjectDependenciesPayload!. Open the type for its fields and nested types.

Field	Type	Description
`pins`	`JSONObject!`	Successful exact pins, including existing pins. Unknown packages and registry failures are omitted.
`persisted`	`Boolean!`	True when eligible pins were written or no eligible write was needed. False means persistence failed; pins retain intended values for retry.
`skipped`	`JSONObject!`	Package names mapped to declaration_changed when caller snapshots are stale.

Types marked with ! cannot be null. Lists use [Type] notation. The type index lists all published input and response types.

Example

mutation ResolveProjectDependencies($input: ResolveProjectDependenciesInput!) {
  resolveProjectDependencies(input: $input) {
    persisted
    pins
    skipped
  }
}

{
  "input": {
    "projectReference": "00000000-0000-4000-8000-000000000001",
    "specifiers": []
  }
}