mouse movements bug

[benmonro]

I get a strange behavior when I move my mouse around the terminal. I've tried this in fish and oh my zsh:

[kenwheeler]

What terminal type are you using?

[akre54]

Getting the same. I'm using iTerm2 in "Full-Width Top of Screen" ("guake") mode with zsh.

My dev start script is "nodemon server --watch server --exec babel-node --plugins transform-es2015-modules-commonjs,transform-object-rest-spread if that makes any difference

[sameerkat]

Also experiencing the same issue with iTerm2.

[kenwheeler]

What do your settings look like? here are mine:

[theverything]

I'm having the same issue and my iTerm settings are the same as yours @kenwheeler

[benmonro]

I'm just using plain old terminal on mac @kenwheeler . I am using oh-my-zsh. Tried it on that as well as fish. both have the same issue.

[eschaefer]

What's interesting for me is that the bug continues in iTerm2 after I kill the dev server as well. Could be related to chjj/blessed#235

FYI:

$ bash --version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin15)

iTerm2: build 3.0.7

[codejunkienick]

I've got the same issue with Termite on Arch Linux.

[kenwheeler]

@akre54 I can reproduce if I run with nodemon. Is everyone here running nodemon?

[brandonmp]

Same, in gnome-terminal and in tilda

Ubuntu 16.04.1
bash v. 4.3.46(1)-release (x86_64-pc-linux-gnu)

I don't think I'm running nodemon, unless it's included in the react-redux-starterkit i'm using--doesn't show up in processes

[kenwheeler]

yeah you're using nodemon if you are using that kit.

[kenwheeler]

Ok, nodemon is the culprit. Issue filed here: remy/nodemon#890 , lets see what @remy has to say. Other suggestions certainly welcome.

[benmonro]

Yep we're using nodemon
On Tue, Aug 16, 2016 at 6:16 AM Ken Wheeler notifications@github.com
wrote:

Ok, nodemon is the culprit. Issue filed here: remy/nodemon#890
remy/nodemon#890 , lets see what @remy
https://github.com/remy has to say. Other suggestions certainly welcome.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#16 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYXhFObGdNRi0msBiwyAvK6l43K6ACyks5qgbgRgaJpZM4Jknol
.

[akre54]

It isn't just with nodemon though. Using babel-node without nodemon has the same issue. Both Terminal.app and iTerm2.

Our app prints debugging info to the console (like queries run), so maybe it's an issue with piping stdout?

[kenwheeler]

I tried babel-node and couldn't reproduce the mouse issue. Maybe I'll just capture stdout and try to filter out control statements.

[kenwheeler]

@akre54 do you know of a way I can identify external stdout?

[akre54]

Not that I'm aware of (short of running the script as a child proces). I'm going to give #27 a try, will let you know how that goes.

[kenwheeler]

That wont fix the nodemon issue. It'll work for child processes that use console, but for anything that uses stdout.write it'll still leak. Whats even stranger is, when using nodemon, if I exit, the server stays running.

[akre54]

Right. I'm wondering if this is useful at all? https://github.com/remy/nodemon#pipe-output-to-somewhere-else

[kenwheeler]

Are you running nodemon using the node api?

[akre54]

I pulled in #27 and it seems to be working to redirect my query logging to the log window (I had to reorder some stuff so that Dashboard was set up before anything got logged). So A+ on that.

I'm still getting the mouse bug with nodemon and plain babel-node too. I'm running the nodemon executable (cli). I was thinking I could create an intermediate script that runs nodemon from the node-api.

[edorivai]

Same here as @brandonmp.
Running:

Ubuntu Gnome 16.04.1 LTS, 64-bit
GNU bash, version 4.3.46(1)-release (x86_64-pc-linux-gnu)

Express with webpack-dev-middleware and webpack-hot-middleware. Dashboard seems to we working fine, apart from this mouse-event printing.

[zrosenbauer]

Also getting this issue, I'll get my env details and pass along.

[kenwheeler]

Can you guys give this a shot #50

[eschaefer]

@kenwheeler unfortunately for my case, #50 did not resolve the issue.

[kenwheeler]

@eschaefer have you tried zsh instead of bash?

[eschaefer]

@kenwheeler: just tried zsh (w/ iTerm2) too, and the problem is the same.

$ zsh --version
zsh 5.2 (x86_64-apple-darwin15.6.0)

[kenwheeler]

@eschaefer can I see your iterm settings page like i posted above? Also, how are you running the dashboard? Can i see a gist of your whole setup from package.json to your server/webpack config?

[eschaefer]

@kenwheeler

iTerm settings:

Dashboard is being launched from an npm script (npm run dev):

"dev": "cross-env NODE_ENV=development sh scripts/dev",

bash script and webpack config file contents are in this gist

[kenwheeler]

Try the new approach in #50, look at the readme updates and use the webpack-dashboard bin in your npm scripts

[eschaefer]

@kenwheeler sorry, totally overlooked the readme updates... updated the gist.

When I run this task alone, it's fine:

./node_modules/.bin/webpack-dashboard -- ./node_modules/.bin/webpack-dev-server --hot --silent --no-info --config webpack/webpack.client.config.js

When I run the full bash script with a parallel server webpack task, then the mouse movement characters get dumped into the terminal:

./node_modules/.bin/webpack --watch --devtool inline-source-map  --silent --config webpack/webpack.server.config.js &
./node_modules/.bin/webpack-dashboard -- ./node_modules/.bin/webpack-dev-server --hot --silent --no-info --config webpack/webpack.client.config.js 

[kenwheeler]

what if you put the dashboard first

[remy]

I'm pretty confident that the PR I've raised against nodemon (expected to
land in nodemon@1.10.1) fixes this.

On Wed, 17 Aug 2016, 22:35 Eric Schaefer, notifications@github.com wrote:

@kenwheeler https://github.com/kenwheeler sorry, totally overlooked the
readme updates... updated the gist.

When I run this task alone, it's fine:

./node_modules/.bin/webpack-dashboard -- ./node_modules/.bin/webpack-dev-server --hot --silent --no-info --config webpack/webpack.client.config.js

When I run the full bash script with parallel webpack tasks, then the
mouse movement characters get dumped into the terminal.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#16 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA1hI-cGcULp59yxPDDAJSJb9cpHan6ks5qg36MgaJpZM4Jknol
.

[kenwheeler]

This should be fixed in the latest release

[remy]

This is back as I had to revert the change. It kinda blew up everyone's use of nodemon! I'll keep investigating. I know what the issue is, the child process is setRaw(true) but I can't detect and forward that from nodemon (though I'm trying stuff).

[edorivai]

I'm still getting the characters printed on mouse events. Using the same environment as before, now with the new setup which runs the webpack-dashboard binary.

For your convenience:

Ubuntu Gnome 16.04.1 LTS, 64-bit
GNU bash, version 4.3.46(1)-release (x86_64-pc-linux-gnu)

[tobbbles]

Experiencing this issue on my system with the following details:

GNU bash, version 4.3.46(1)-release (x86_64-unknown-linux-gnu)
Arch Linux x86_64
i3 version 4.12-non-git
termite v11

[tom76kimo]

After updating nodemon and webpack-dashboard, still encounter with this issue as well. Using iTerm2

[davefedele]

Changing iterm2 'report terminal type' to ANSI stops the mouse movements bug.

However, now I can't scroll :(

[cimi]

Changing iterm2 'report terminal type' to ANSI stops the mouse movements bug.

I can confirm this. It is inconvenient, though.

I'm running it on OSX 10.10.5 with iTerm2, settings identical to the ones recommended on this post. The project was bootstrapped from react-redux-starter-kit about six months ago. I've tried plugging in the dashboard via the recommended way (through the binary).

This issue should probably be re-opened since the issue still persists.

[pie6k]

It happens when there are 2 or more processes active in one console thread. (Not sure if I call it properly)

For example, in my package.json, I've got commands:

  "scripts": {
    "start": "node server.js",
    "lint": "eslint src",
    "gulp": "gulp",
    "dev": "gulp | webpack",
    "webpack": "webpack-dashboard -- node server.js"
  },

If I call npm run dev - issue occurs (there is also gulp command running). If I run npm run webpack - there is no issue (webpack-dashboard is running alone).

[flipflopsandrice]

Indeed, as @pietrasiak noticed, it happens when starting two processes in one thread.
Tested in Terminator, Guake and GNOME Terminal. All with zsh.

"scripts": {
  "serve:dev": "webpack-dashboard -- webpack-dev-server --open --env dev & cd node_modules/api-mocks && DEBUG=-* yarn run start",
}

Using a package like concurrently makes no difference (obviously).

[kenwheeler]

@flipflopsandrice you can run it standalone now, this should only happen using the old syntax where you pass a process. Otherwise it runs on its own and gets data via sockets. Doing it the old way, shown above, does some weird thing with stdout

[flipflopsandrice]

@kenwheeler Thanks, I fixed it by adding a separate npm script:

"scripts": {
  "dev:dashboard": "webpack-dashboard -- npm run serve:dev",
  "serve:dev": "webpack-dev-server --open --env dev & cd node_modules/api-mocks && DEBUG=-* yarn run start",
}