wave-binder-cli
Use the wizard to populate the previously created protonodes.json by adding/editing nodes in a guided flow.
Configure Wave Binder, connect your backend, and test a first flow with dependent nodes.
npm install wave-binder
extapi.json){
"target": "http://localhost:3000/api",
"secure": false,
"authorization": null
}
protonodes.json (placeholder)[]
At this stage, keep the file empty. Node definition is handled in the WaveBinder ecosystem integration path (CLI wizard) or in the ProtoNodes Guide.
import { WaveBinder, ComplexNode } from "wave-binder";
import EXT_API_CONFIG from "./extapi.json";
import LICENSE from "./license.json";
import PROTO_NODES from "./protonodes.json";
const extApis = new Map();
extApis.set("api", EXT_API_CONFIG);
export const wb = new WaveBinder(LICENSE, PROTO_NODES, extApis, []);
wb.tangleNodes();
wb instance must be created in a shared accessible place (for example, a shared module/service singleton) and then reused.
Avoid creating it inside components or functions that may run multiple times, otherwise you may get multiple instances and inconsistent state.
extApis.set("api", ...) registers the service referenced by serviceName: "api".extApis.set("api", ...) must exactly match serviceName in nodes (e.g. "api")."backend"), update nodes to serviceName: "backend" too.wb.tangleNodes() connects dependencies and starts the reactive flow.Beyond the wave-binder library, you can integrate official components to speed up setup and maintenance:
protonodes.json file created in step 3 (guided node create/edit).Use the wizard to populate the previously created protonodes.json by adding/editing nodes in a guided flow.
Installation, DB configuration, table exposure, and project integration.
protonodes