Troubles running example scripts on Mac about node-monitor HOT 5 CLOSED

Hey Christopher,

The initial command was working as expected:

$ node
> var Monitor = require('monitor');
undefined

undefined is actually what the REPL displays whenever you assign a variable. Try this:

$ node
var a = 'hello';
undefined

From that point on, things went downhill fast. Running require('./node_modules/monitor/monitor.js'); starts the monitor server (cool!). It's the same as going into the monitor directory and entering

$ node monitor.js

Unfortunately this isn't the same as var Monitor = require('monitor'); because it doesn't assign the Monitor class to your variable. From that point on, the Monitor variable doesn't represent a class that you can new, so things didn't work very well.

Try running the commands in the REPL window just as they're shown in the example. I will update the example to show the undefined return from the first command, because I can see how this can be confusing.

from node-monitor.

Aha! I should have known better. Thanks for working with a newb. ;)

The REPL example is working great! I'm seeing a memory change reported every second. The JSON data is exactly what I'm after for my custom app.

AHA! I figured it out. In the documented js example:

var Monitor = require('monitor');

needs to change to:

var Monitor = require('monitor').start();

Then I'm seeing stuff after adding a few test log messages (showing onchange being fired every 10 seconds as expected!).

Would you like me to attempt a pull-request? 💃

Thanks again.

from node-monitor.

Adding .start() to the end of require('monitor') starts the monitor server within the REPL, which is cool, but not necessary for this client-side example. The start() command is necessary in your server, which should be running in another process while running the client-side example.

Does this make sense?

from node-monitor.

Yes, I think that makes sense. Since I'm creating a server script and not something that would run in the browser client (my server will talk to the browser client with this info and details from other services), I need to start it for the server. The client that connects to my server will not need that (and actually won't use it directly in my case).

Thanks for the clarification and assist!

from node-monitor.

I'll go ahead and close this.

from node-monitor.