Hyper don't start in dev mode

[linonetwo]

I'm on latest Canary branch

• OS version and name: MacOS 10.13.6
• The issue is reproducible in vanilla Hyper.app: Is Vanilla

  Issue

  I'm trying "Contributing" section of README, running yarn yarn dev and yarn app or using VSCode's debugger.

Electron icon is shown, but no hyper window comes out.

[romainlq]

Do you have any message in the debugger ?

[linonetwo]

Shows:

Debugger listening on ws://127.0.0.1:28637/21f7da79-8561-490c-b15c-97a3d01bfd8e
Debugger attached.
Plugin hypercwd (1.2.3) loaded.
plugins.js:288
Plugin hyper-quit (1.0.3) loaded.
plugins.js:288
Plugin hyperpower (1.0.0) loaded.
plugins.js:288
Plugin hyper-folder-icon (1.5.2) loaded.
plugins.js:288
Plugin hyper-visual (2.1.5) loaded.
plugins.js:288
Plugin hyper-transparent-dynamic (1.2.0) loaded.
plugins.js:288
plugins have changed / not init, scheduling plugins installation
plugins.js:181
Disabling Chromium GPU blacklist
index.js:89
running in dev mode
index.js:94
electron will open file:///Users/linonetwo/Desktop/repo/hyper/app/index.html
index.js:109
Launching yarn: /Users/linonetwo/Desktop/repo/hyper/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron /Users/linonetwo/Desktop/repo/hyper/bin/yarn-standalone.js install --no-emoji --no-lockfile --cache-folder /Users/linonetwo/.hyper_plugins/cache

install.js:17
Plugin hypercwd (1.2.3) loaded.
plugins.js:288
Plugin hyper-quit (1.0.3) loaded.
plugins.js:288
Plugin hyperpower (1.0.0) loaded.
plugins.js:288
Plugin hyper-folder-icon (1.5.2) loaded.
plugins.js:288
Plugin hyper-visual (2.1.5) loaded.
plugins.js:288
Plugin hyper-transparent-dynamic (1.2.0) loaded.
plugins.js:288
[Notification] Plugins Updated: Restart the app or hot-reload with "View" > "Reload" to enjoy the updates!

And Electron Icon in the docker, but no window pops up.

[romainlq]

What if you start it with no plugin at all?

Or maybe there is already a node process running background?

[linonetwo]

Restart and remove all plugins from .hyper.js still no good. Maybe it's MacOS' fault...