The `node-opcua-service-node-management` package is a core component of the pure Node.js OPC UA SDK, providing the essential structures and types for managing nodes within an OPC UA Address Space. As part of the actively developed `node-opcua` ecosystem (current stable version 2.169.0), it handles the OPC UA services for adding and deleting nodes programmatically. The library maintains a rapid release cadence, typically releasing new features and stability improvements every few weeks. Key differentiators include full OPC UA 1.05 compliance, significant performance optimizations in data type handling and transport layers, robust certificate management capabilities, and support for advanced deployment scenarios like advertised endpoints for Docker/NAT environments. This module specifically exposes the request and response message types for the Node Management Service Set, enabling developers to build OPC UA servers that can dynamically modify their address space.
npm install node-opcua-service-node-managementVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to initialize an OPC UA server and use `AddNodesItem` to define and add a new folder node to its address space dynamically. It illustrates the structure for client-initiated node creation requests.
Review your code for reliance on deprecated `async` or `lodash` utilities if you encounter unexpected behavior. Ensure your Node.js environment is up-to-date with versions supporting modern JavaScript features.
Update `ApplyChanges` event listeners to include `ISessionContext` in their function signature if you wish to leverage or avoid issues with the new context parameter. Example: `(item: any, context: ISessionContext) => { ... }`.Regularly update your Node.js runtime environment to the latest stable and patched versions. Pay attention to security advisories for both `node-opcua` and Node.js itself.
On the OPC UA server, explicitly enable node management capabilities if you intend for clients to dynamically modify the address space. Consult the server's specific configuration or `node-opcua`'s server setup documentation.
Ensure that `server.engine.addressSpace.setNodeManagementEnabled(true);` (or similar for other SDKs) is called during server initialization and that the client's user identity has appropriate access rights.
Use the correct `NodeAttributes` subclass, e.g., `new ObjectAttributes({ displayName: { text: 'My Object' } })` for `NodeClass.Object`.Verify that `node-opcua-service-node-management` is listed in your `package.json` and installed (`npm install` or `pnpm install`). Check the import statement for typos and ensure your `tsconfig.json` correctly resolves modules.
No dependency data recorded yet.