A package is a versioned collection of nodes and graphs that Fusion loads into System Modeler. Packages group related nodes into categories so you can find the operation you need and combine nodes from different areas of Fusion in a single graph.
There are two kinds of packages:
Most graphs use nodes from more than one package. A graph might read a value with a System node, transform it with Base math and logic nodes, then create geometry with a Design node. Higher-level packages can build on lower-level ones: Manufacture nodes can use Design, System, and Base nodes, and Design nodes can use System and Base nodes.
When you add a node or reusable subgraph from another package to a graph, a formal dependency on that package is established. Dependencies are stored in the package's package.manifest file, which records each required package and its version. The Manufacture package, for example, lists Base, System, and Design as dependencies because its graphs and nodes rely on all three.
Circular dependencies aren't allowed. A package can't depend on a package that depends on it.