transport

Hi,

For safety use, it's better to have null check for all variables which are used in this function.

if (!_sessionPriv.$clientAlarmList) {
    return;
}

↓

if (!_sessionPriv.$clientAlarmList
     || !_sessionPriv.$monitoredItemForAlarmList
     || !_sessionPriv.$subscriptionforAlarmList ) {
    return;
}

https://github.com/node-opcua/node-opcua/blob/master/pack

We recently added the Map::validCoords function. This should be used in a number of locations. Search the codebase for the constant 0x2FFF, 12287, 0x3000 or 12288 and if its a Map::Pos2 or Pos3 then it very likely should be using the validCoords function.

Likewise if its 384, 0x180, or 0x17F, 383 and if its a Map::TilePos2 then it should probably also be using the validCoords functi

Currently, WebSocket is working for client/server side. However, the browsers do not allow to create tcp connections direclty (which is the current implementation based). Instead, the web-sys must be used.

• Use a different WebSocket implementation if the target is wasm.
• wasm example of a client.

When adding multiple rpc target classes, if multiple targets contain the same\similar method, the method in first target added is used (as documented). But I miss an option to disallow duplicates, as this is (in my case) always an error. Alternatives:
-Preferably a setting on JsonRpc itself that produce error when AddLocalRpcTarget is called
-A setting on JsonRpc itself that produce error during