A quick look is generally not enough to understand the project…
node-Tor is a nodejs module, works inside browsers and nodejs environment of course
The use cases are numerous, please see some examples here GitHub - Ayms/node-Tor: Javascript implementation of the Tor (or Tor like) anonymizer project (The Onion Router) and Convergence-2020, one of them is to use browsers as Tor nodes, which is different from Snowflake where browsers just relay the messages, node-Tor creates Tor circuits from the browsers directly
You can package node-Tor as Electron for example or as a browser extension but I don’t see the point of bridging with the Tor daemon, neither the use of a SOCKS proxy which is dangerous, see bitcoin CVE-2017-18350
It must be understood that the js node-Tor inside browsers do not browse as explained above, do not interact with a web server, it’s an independant and secure webapp inside browsers with zero dependencies, everything is embedded in a single js code, therefore known web vulnerabilities like XSS, WebRTC deanonymization, etc do not apply, the only important thing is to be sure about the code loaded as explained above again (Discover and move your coins by yourself), you can also include the code as a bookmarklet and run it just clicking on a button in the browser tab so nothing is loaded from the outside
I don’t know for the Arti wasm but I am still super skeptical that this will work correctly (or even that they will succeed to do it) and will not use SOCKS to bridge with a non browser daemon, and that this will be optimized for browsers, and that this will give the level of control that provides node-Tor