zeromq.js | : zap : Node.js bindings to the ØMQ library | Runtime Evironment library

I am trying to implement a pub/sub broker with ZeroMQ where it is possible to restrict clients from subscribing to prefixes they are not allowed to subscribe to. I found a tutorial that tries to achieve a similar thing using the ZMQ_XPUB_MANUAL option. With zeromq.js it is possible to set this option:

The documentation for connect method says,

Connects to the socket at the given remote address and returns immediately. The connection will be made asynchronously in the background.

But, await does not seem to be applicable as shown in their example of subscriber code.

subscriber.js

I am doing the example of pubsub from this link and managed to get it work.

server.js:

Consider a Node.js application with few processes:

• single main process sitting in the memory and working like a web server;
• system user's commands that can be run through CLI and exit when they are done.

I want to implement something like IPC between main and CLI processes, and it seems that ZeroMQ bindings for Node.js is a quite good candidate for doing that. I've chosen 6.0.0-beta.4 version:

Version 6.0.0 (in beta) features a brand new API that solves many fundamental issues and is recommended for new projects.

Using Request/Reply I was able to achieve what I wanted: CLI process notifies the main process about some occurred event (and optionally receives some data as a response) and continues its execution. A problem I have right now is that my CLI process hangs if the main process is off (is not available). The command still has to be executed and exit without notifying the main process if it's unable to establish a connection to a socket.

Here is a simplified code snippet of my CLI running in asynchronous method:

I'm trying to install ZeroMQ into an electron application but I'm unable to rebuild the package for electron.

I'm trying to install ZeroMQ for electron 5.1.0 on my Windows 10 machine. Details:

OS: Windows 10 Electron: 5.0.8 node: 12.0.0

As per the instructions in the README.md https://github.com/zeromq/zeromq.js/, I have followed this procedure:

1) Install zeromq with npm npm install zeromq

2) Rebuild for electron npm rebuild zeromq --runtime=electron --target=5.1.0 Notes: The documentation indicates that the target here is supposed to be the Electron version; however, this causes a 404 error as npm tries to go to https://nodejs.org/dist/v5.0.8/node-v5.0.8-headers.tar.gz which doesn't exist. I then thought to try the node version, but that leads to a 401 error. I then tried the zeromq version (5.1.0 as shown in command) which leads to this error:

error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

Googling this error brings up a lot of StackOverflow problems where the build tools are required. Looking a little ahead on the README.md led me to thing I could solve this problem using the next command.

3) Install visual studio build tools npm install --global --production windows-build-tools This command is completed successfully and installs both the build tools and python2.7

4) Rerunning the rebuild command in step 2 leads to the same error. I tried variations of this command: npm config set msvs_version 2013 using 2015 and 2017 as well.

2013 and 2015 give this error: error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk. gyp ERR! build error gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe failed with exit code: 1 gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23) gyp ERR! stack at ChildProcess.emit (events.js:198:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12) gyp ERR! System Windows_NT 10.0.17134 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" gyp ERR! cwd C:\Users\\path\to\app\node_modules\zeromq gyp ERR! node -v v10.16.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! zeromq@5.1.0 install: node scripts/prebuild-install.js || (node scripts/preinstall.js && node-gyp rebuild) npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the zeromq@5.1.0 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

While 2017 gives this: error MSB8020: The build tools for v140 (Platform Toolset = 'v140') cannot be found. To build using the v140 bui ld tools, please install v140 build tools. Alternatively, you may upgrade to the current Visual Studio tools by select ing the Project menu or right-click the solution, and then selecting "Retarget solution". [C:\Users\\path\to\app\node_modules\zeromq\build\zmq.vcxproj] with a similar ending section as the other years produced.

To make a long story short, I'd like to run my jest tests (using CLI) with electron instead of node.

It's relevant when using native module, because you need to build them using electron header while jest run them using plain node. So I must either build my native modules for my app (at least in dev mode) or my tests, I can't have both to work.

In this thread they propose to use mocha, but I want to use jest, which is far more advanced and interact well with React. Note that I don't want to mock the native module, since I write integration tests.

I opened an issue about the zmq github repo. One proposed solution is "to target your tests using ELECTRON_RUN_AS_NODE=true electron as your node runtime". This is a very good solution, since using electron will both make the test environment closer to the execution environment and solve my specific issue with native modules.

I'd like to apply that, but I do no seem to be able to setup the jest CLI to use electron instead of node, and I have no idea where to start. Maybe I should run jest programmatically without the CLI ? But I might lose the nice test filtering features of the CLI.

Has anyone solved this already?

I'm building a HTML page which renders a graph created using VivaGraph ( https://github.com/anvaka/VivaGraphJS ) .

This graph should be fed by data coming from a ZMQ (ZeroMQ) datastream, where my webpage is connected as "Subscriber" to a "Publisher"; the perfect example code is here: https://github.com/zeromq/zeromq.js/#pubsub

The problem is: VivaGraph is for JS on client side while ZMQ is for NodeJS environment.

How can bind my VivaGraph graph to the ZMQ data stream in the client side?

I have a python program that will accept a ZeroMQ REQ Requester and provide a number of functionalities, based on the given code.

So if a client sends a code 02, python will return back a memory statistics, 03 a CPU statistics and so on.

The client is created with nodejs and zeromq.js, in order to communicate with the backend. I am not sure what the best way would be to send multiple messages from the frontend, since I will send multiple such messages with different codes each second.

What I have now is something similar to this: