nothing happens after this. Node doesn't start

I have no output in the stdout view, when doing

const spinner = [ '⠋', '⠙', '⠹', '⠸', '⠼', '⠴', '⠦', '⠧', '⠇', '⠏' ];
process.stdout.write(" "+spinner[ (index+1)% spinner.length ]+"\r" );

As shown above, CPU usage is not rounded off. This may cause wrapping which might look less appealing. Consider rounding the number to a maximum of decimals to prevent this.

Not sure this can be fixed or not

Add the ability to Pause, Rewind and Fast Forward Graphs with simple key interface.

Give details about the platform the Node app is running on.

No stats are collected when using nodemon. The dashboard app spawns the nodemon process which then spawns the actual node app. This is a bit different from using nodemon to reload the dashboard app if it terminates. (from issue #9)

Repo steps

1. Install nodemon in the project. yarn add -D nodemon
2. Execute test app with nodemon: node bin/nodejs-dashboard.js -- node_modules/.bin/nodemon --exec "node test/app/index.js"

I'm curious about the risks related to using this package.

The docs say not to use it in production, but without outlining what the encountered or anticipated problems with the current version might be.

Providing an outline of risks can help a developer understand your reasons for this suggestion, enabling them to determine for themselves if those concerns are applicable for their project and at what point in their pipeline from dev/lab to stage to prod this should be removed.

I currently exit using Ctrl + C (Ubuntu OS) - is that the correct way to exit or is there a more elegant way?

This is my Procfile for my LoopbackJS app:

web: nodejs-dashboard node .

The problem:
If I run nf start, the console just clears and nothing shows up (Not even an error). My app uses a bunch of environment variables and foreman really makes it a breeze to run it.

The expected result:
The dashboard should appear in the terminal running the app. This actually does happen if I run nodejs-dashboard node . instead of nf start, it just fails with foreman.

since this is node 4+ only.

I love your module, however before my console logs were colored, as I am using Chalk. It is really important as it helps make the output clearer.

Please enable compatibility.

Thank you and keep it up!

<praise>Splendid package, well done</praise>

My application uses Bunyan for logging. In order to make the output more readable, my original command is node ./app.js | bunyan.

When I change my command to nodejs-dashboard node ./app.js | bunyan, I just get the message "Waiting for client connection on 9838..." and nothing else.

If I get rid of the | bunyan pipe, it works fine (but with the stdout an unreadable mess).

Any ideas how to get my output piped?

greenkeeper just notified me that there's a 0.3.0 version available for this project, but I'm not seeing anything about 0.3.0 in this repo.

I also don't see any tags or releases of any kind, or any CHANGELOG to indicate what changed between 0.2.1 and 0.3.0.

can you provide some info on what changed and confirm that this was a legitimate publish to npm?

• Node Version: Node v6.9.1
• Package version: v0.1.1
• Platform: SMP Debian 3.2.81-1 x86_64 GNU/Linux
  When I required this package, the memory began to grow slowly
  const dashboard = require("nodejs-dashboard");
  Memory schedule
  
  Comparison of 2 heap shapshots
  

30m for cpu/event loop/memory graphs when they're full width.
Probably don't want to store individual per-second values, so would need to add aggregation to provider.

Just installed nodejs-dashboard globally, but I'm getting error.

Command: nodejs-dashboard -- node -r nodejs-dashboard index.js

Error code:

RangeError: "size" argument must not be negative
    at Function.Buffer.alloc (buffer.js:229:3)
    at new Buffer (buffer.js:152:19)
    at new Canvas (C:\Users\User\AppData\Roaming\npm\node_modules\nodejs-dashboard\node_modules\drawille-blessed-contrib\index.js:17:18)
    at new Context (C:\Users\User\AppData\Roaming\npm\node_modules\nodejs-dashboard\node_modules\drawille-canvas-blessed-contrib\index.js:11:18)
    at module.exports.Canvas.getContext (C:\Users\User\AppData\Roaming\npm\node_modules\nodejs-dashboard\node_modules\drawille-canvas-blessed-contrib\index.js:274:24)
    at Line.<anonymous> (C:\Users\User\AppData\Roaming\npm\node_modules\nodejs-dashboard\node_modules\blessed-contrib\lib\widget\canvas.js:22:29)
    at Line.EventEmitter._emit (C:\Users\User\AppData\Roaming\npm\node_modules\nodejs-dashboard\node_modules\blessed\lib\events.js:98:20)
    at Line.EventEmitter.emit (C:\Users\User\AppData\Roaming\npm\node_modules\nodejs-dashboard\node_modules\blessed\lib\events.js:117:12)
    at emit (C:\Users\User\AppData\Roaming\npm\node_modules\nodejs-dashboard\node_modules\blessed\lib\widgets\node.js:109:15)
    at Box.Node.insert (C:\Users\User\AppData\Roaming\npm\node_modules\nodejs-dashboard\node_modules\blessed\lib\widgets\node.js:111:5)

This is more likely an issue on the ts-node side of things, but I'm not sure how the chart statistics are obtained to open up a topic over there.

Really nice work! I'm just opening this issue to submit an idea.

For applications that maybe have multiple processes running, what do you think about enabling tabs? Perhaps each application running could register itself to a display name and you could toggle between them using numbers. I could imagine spawning child processes that might render a new tab and then when it closes the tab disappears. Also for use with projects like https://github.com/strongloop/node-foreman, where you might have two process (web/worker) running and want to run them together.

Some ways it may work:

• Pass a name on require, but this would break the current child.stdout approach (it might need to monkey patching process stdout instead)
• Pass a flag to nodejs-dashboard --new-tab web that'll use the parent dashboard process to attach to it (this would likely mean a new tab results in two tabs - one for the overall process, one for the new tab child)

I'm seeing question mark ? instead of those nice dots.

I've used SourceCodePro+PowerLine+Awesome Regular font in my terminal also.

RangeError [ERR_INVALID_OPT_VALUE]: The value "-63" is invalid for option "size"

Have a look at these two screenshots:

vs

It seems the ansicodes and unicode characters of mocha are beeing striped?

Check this gist for reproduction:

https://gist.github.com/enko/31be945ca47b0c481275e76a2b695714

Run docker-compose build and then docker-compose run test_runner alternativly append -f docker-compose_colors.yml to run it without nodejs-dashboard.

This also repros #10.

Thanks for your time for this nice product!

nodejs-dashboard babel-node index.js works fine.

Dunno how to use it with both nodemon and babel-node.

This is the raw command i used earlier btw: nodemon index.js --exec babel-node

This is more of an idea and/or feature request, if at all possible. It would be useful to have this data while developing a Meteor application.

Thanks for the tool!

Text is not selectable in the stdin and stdout stream. I guess it might be related to this chjj/blessed#263 but I'm not sure wether it's my config or it's more general.

It's not selectable in both iTerm and Terminal

Apparently, Travis hasn't run in 8 months: https://travis-ci.org/FormidableLabs/nodejs-dashboard/builds

Our config looks OK, but something's wrong as it's not running.

When I run my app, I get the following error. (Installed the dashboard following the directions in the README from the repo.)

Failed to compile.

Error in ./~/nodejs-dashboard/~/pidusage/lib/stats.js
Module not found: 'child_process' in /Users/igreulich/apps/rhinofront/node_modules/nodejs-dashboard/node_modules/pidusage/lib

 @ ./~/nodejs-dashboard/~/pidusage/lib/stats.js 4:11-35 5:12-36

This is during the webpack build process. (I started the app with create-react-app but have since ejected it, am adding niceties.)

I'm anecdotally seeing a lot of failures like:

  68 passing (24s)
  2 failing
  1) MetricsProvider _onMetrics retains metrics received, while aggregating them into time buckets:
     Error: Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
  
  2) MetricsProvider _onMetrics aggregates data for non-uniform data sets too:
     Error: Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

in Travis. Current incarnation: https://travis-ci.org/FormidableLabs/nodejs-dashboard/jobs/311447216 (I'm restarting this build so it may pass next time...)

added import to my server entrypoint:
import 'nodejs-dashboard';

added npm script like so:
"start:dev": "NODE_ENV=development nodemon --watch server --exec \"npm run build:schema && nodejs-dashboard babel-node server/index.js\""

get these escape characters after running for a minute or so:

this only occurs when my terminal is in rxvt mode, not in ansi mode.

I am consoling to stdout and stderr but dashboard updates with none of them. My index.js code is as follows:

require('nodejs-dashboard')
const http = require('http')  
const port = 4000

const requestHandler = (request, response) => {  
  console.log('Printing on stdout: ',request.url)
console.error('Printing on stderr')
  response.end('Hello Node.js Server!')
}

const server = http.createServer(requestHandler)

server.listen(port, (err) => {  
  if (err) {
    return console.log('something bad happened', err)
  }
  console.log(`server is listening on ${port}`)
})

The following should appear on stdout:

server is listening on 4000
Printing on stdout:  /

While I expect this line on stderr:
Printing on stderr

But this is what my dashboard looks like:

I would ideally not want to touch my package.json/code base at all and run the dashboard via the binary itself.
Is it possible?
I did
nodejs-dashboard npm start It loads the dashboard but does not update the memory and processor usage part.

From @parkerziegler

"escape"and"q"as valid keys to trigger sendingSIGINT`.

It might be overkill depending on the scope of monitoring that your looking to provide, but it might be worth looking at appmetrics as a source of monitoring data. The project is here:
GitHub: https://github.com/RuntimeTools/appmetrics
NPM: https://www.npmjs.com/package/appmetrics

I have the following command in package.json -> "dev": "nodejs-dashboard node bin/server.js --env development"
The issue is that --env development doesn't get forwarded to server.js.

I've tested and the issue is that commander strips it and only keeps the command itself.

I'll try and provide a PR if I find the time!

LE: I know you can use "dev": "nodejs-dashboard -- node bin/server.js --env development" but I think it would be nice if it worked directly.

Thanks for the great work. I'm just curious, where/how is the event loop monitoring happens? any reference to a code file/article will be appreciated

I suggest we find a way not to require it in index.js (you do suggest to install it as dev dependency which would mean it is not available in production)

possible solutions:

• wrap it in a logical test on the environement >> not ideal, and bloat
• wrap it in a separate dev.index.js which then loads index.js
• ...

Provide the ability to find a specific time in the graphs.

This tool is awesome but I noticed that when I tried to get it running with an existing project the dashboard would display but nothing would run as the project supports Node v5.X while using harmony flags.

Works: "dashboard": "nodejs-dashboard node server.js"
Doesnt Work: "dashboard": "nodejs-dashboard node --harmony_destructuring server.js"

Not sure if the intention is that nodejs-dashboard would only support Node v6 and above (understandable) or if this is a bug/misunderstanding. If it is a bug I would be happy to try and get to the bottom of it when I have some free time later.

In the layout with cpu / event loop history

After installing and configuring the library, I ran some requests but it's not indicating in the terminal.

How do i go about that?

Hi, i have no Scrollbars in my ConEmu on Window 10 and cant scroll any
when i console.log some arrays/object it would be helpfull but i think its a windows problem xD
here a screen:
https://gyazo.com/beab152e51d0945c14b458e2161c1676

//e but i think its a problem from https://github.com/chjj/blessed

I did:
"npm install nodejs-dashboard --save-dev"
added "require('nodejs-dashboard')" to the top of my app.js
ran "nodejs-dashboard node app.js" from the command-line and get this error:

"bash: nodejs-dashboard: command not found"

EDIT: Ran it in a npm script and it's beautiful. This will be on one of my monitors for all the projects I work on.

After resizing the terminal, both the outputs and the graphs are resized as well. Only the outputs use this new space, the graphs stay small.

Tested with 1.0.1 on Ubuntu Trusty LTS (14.04)

mac OS 10.13.3
node v 8.9.1
Tried on Hyper and iTerm

npm install -g nodejs-dashboard
nodejs-dashboard -- node -r nodejs-dashboard test.js

This starts the dashboard but gives me an error accessing the module...

Hello! Your work is awesome, but I've found it can not work in git-bash, all the output are mess code. Are there anything I did wrong, or nodejs-dashboard doesn't support git-bash yet?
Thanks！