NodeOPCUA API Documentation
    Preparing search index...

    Enumerating the nodes a namespace holds.

    The iterators walk the namespace's own index, so they yield only nodes belonging to this namespace, in insertion order, and they do not follow references into any other. A count is a plain size lookup rather than a walk, so preferring it to [...iterator()].length is worth doing on a large model.

    None of these iterators tolerate the namespace being modified while one is open, for the same reason a Map iterator does not: adding or removing a node invalidates it. Collect into an array first when the loop body adds nodes.

    interface INamespaceIterable {
        _aliasCount(): number;
        _dataTypeCount(): number;
        _dataTypeIterator(): IterableIterator<UADataType>;
        _objectTypeCount(): number;
        _objectTypeIterator(): IterableIterator<UAObjectType>;
        _referenceTypeCount(): number;
        _referenceTypeIterator(): IterableIterator<UAReferenceType>;
        _variableTypeCount(): number;
        _variableTypeIterator(): IterableIterator<UAVariableType>;
        aliasCount(): number;
        dataTypeCount(): number;
        dataTypeIterator(): IterableIterator<UADataType>;
        nodeIterator(): IterableIterator<BaseNode<BaseNodeEvents>>;
        objectTypeCount(): number;
        objectTypeIterator(): IterableIterator<UAObjectType>;
        referenceTypeCount(): number;
        referenceTypeIterator(): IterableIterator<UAReferenceType>;
        variableTypeCount(): number;
        variableTypeIterator(): IterableIterator<UAVariableType>;
    }

    Hierarchy (View Summary)

    Index