The `node-opcua-nodeset-ua` package is a core component of the `node-opcua` SDK, providing the standard OPC UA NodeSet XML definitions. These definitions are essential for building OPC UA servers that expose a semantically rich address space conforming to the OPC UA Unified Architecture specification. As part of the highly active `node-opcua` monorepo, it receives frequent updates, typically bi-weekly, aligning with the project's 'Perpetual Beta' model. The current stable version is 2.169.0. Key differentiators for the `node-opcua` ecosystem, including this module, include its pure Node.js implementation, extensive TypeScript support, and a focus on industrial IoT (IIoT) and Machine-to-Machine (M2M) communication. It allows developers to load standard and custom information models into an OPC UA server's address space for robust data exposure.
npm install node-opcua-nodeset-uaVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to set up a basic OPC UA server and load the standard NodeSet 2.0 information model using `node-opcua-nodeset-ua` to establish a foundational address space.
Review custom code and plugins for direct dependencies on `async` or `lodash` utilities. Refactor to use native JavaScript asynchronous patterns (e.g., `Promise`, `async/await`) and built-in array/object methods.
Validate custom NodeSet XML files and DataType definitions against OPC UA 1.05 specifications. Test existing server implementations thoroughly to ensure data types are correctly recognized and handled, especially for complex structures and unions. Consult the `node-opcua` documentation for updated guidance on custom DataType registration.
Review and update certificate management logic in clients and servers. Ensure that `TrustListClient.addCertificate` is used correctly with certificate chains if applicable. Familiarize yourself with the `OPCUACertificateManager` API and best practices for secure certificate handling, including proper PKI setup and trusted/rejected certificate store management.
When deploying `node-opcua` servers in containerized or proxied environments, explicitly configure the `advertisedEndpoints` option in the `OPCUAServer` constructor to reflect the externally accessible URLs. This ensures clients receive the correct network information for connection.
Ensure that both OPC UA client and server machines have their system clocks synchronized, ideally using NTP (Network Time Protocol). Address any `[NODE-OPCUA-W33]` warnings by rectifying time discrepancies to prevent potential connection instability.
Convert your project or specific files to ES Modules by adding `"type": "module"` to your `package.json` or by using `.mjs` file extensions. Then, use `import { standardNodeSet2 } from 'node-opcua-nodeset-ua';` syntax. If a mixed environment is required, consider dynamic `import()` or a build step to transpile to CommonJS if strictly necessary.Ensure the peer's certificate (or its Certificate Authority's certificate) is correctly placed in the `trusted/certs` directory of your client's/server's PKI store. For self-signed certificates, both sides typically need to trust the other's certificate. Verify certificate dates and revocation status. `node-opcua` provides tools (e.g., `node-opcua-pki`) to manage certificates.
Verify the exact symbol name and the import path. The common import is `import { standardNodeSet2 } from 'node-opcua-nodeset-ua';`. Check the `node-opcua-nodeset-ua` package for available exports in your installed version. If using older `node-opcua` versions, the export name or module structure might differ.Double-check the file path provided to `nodeset_filename`. Ensure the XML file is valid and correctly formatted, typically UTF-8 encoded, and accessible by the Node.js process. Tools like XML validators can help diagnose malformed files.
No dependency data recorded yet.