Endpoint.js uses node-uuid to create a unique identifier for itself every time it starts up. It also uses it to create unique stream identifiers used in the link layer, and host identifiers used in the switching layer (for external hosts)
The newer version of node-uuid (1.4.7) outputs an extremely annoying warning when used in a web-worker stating that the Javascript implementation of Math.random() is vulnerable and broken. This is a well known fact, but since I'm not using this uuids for anything critical, I think it's fine. I manually set the package.json file to 1.4.3.
We need to either figure out a way to stop the warning, or use another uuid implementation.
datasedai
commented
7 years ago
Endpoint.js uses node-uuid to create a unique identifier for itself every time it starts up. It also uses it to create unique stream identifiers used in the link layer, and host identifiers used in the switching layer (for external hosts)
The newer version of node-uuid (1.4.7) outputs an extremely annoying warning when used in a web-worker stating that the Javascript implementation of Math.random() is vulnerable and broken. This is a well known fact, but since I'm not using this uuids for anything critical, I think it's fine. I manually set the package.json file to 1.4.3.
We need to either figure out a way to stop the warning, or use another uuid implementation.