Skip to main content

List a project's nodes using one of its own libraries

GET 
/api/project_library_dependents

Every node in one project pinned to one of the project's own libraries, with whether each is behind the named version.

The read behind "you published 2.0.0 - these five nodes are still on 1.0.0". Publishing snapshots a version and nothing more: the nodes that use the library keep resolving the one they named, so adopting it is a separate decision, and one that cannot be made without first being told which nodes it concerns.

Scoped to a project because a project library is: another project's library of the same name is unrelated code that happens to share it.

Read from the hub, like its catalog counterpart - the question is which nodes the project has, not which ones the caller has edited locally and not yet committed.

Request​

Responses​

Successful Response