Does not install properly with Yarn #23
Comments
Thanks for your report! |
Getting the same error on Ubuntu 16.04 also. |
MacOS High Sierra 10.13.5, close to the same error.
|
I'm experiencing this on
|
@mavame , could you try to run ndb with NDB_DEBUG_FRONTEND=1 flag? NDB_DEBUG_FRONTEND=1 ndb . |
Also getting a blank screen on macOS, running it with
|
@fooey , thank you. It looks like ndb installation failed. npm -g uninstall ndb && npm install -g ndb |
I installed it using yarn originally, but I uninstalled it and used npm instead, and it does seem to be working now. Uninstalled it from npm, and tried again with yarn to see if it generated any logs, but it works now. Don't know why it wasn't happy before, but thanks for the help. |
I just tried this as well, and it's working just fine for me now. Sounds like maybe yarn skips some dependency or compile step on the first go, but npm handles it fine. In any case, my most recent install of ndb with yarn is working fine now. |
Thanks! We will take a look into installing with yarn. |
I'm seeing this intermittently using npm to [un]install.
|
Most likely we do something wrong with installation scripts. I will take a look. |
1.0.9 should contain fix for yarn and black screen. I will be happy to get feedback! Feel free to reopen this one if it is still reproducible. |
@ak239 I encountered this issue again today, running a fresh install through yarn on a fresh Ubuntu 18.04 installation. Removing, installing with npm, removing, then installing with yarn again fixed it, as before. EDIT: I should also note, this time running |
* fix(build): publish prebuilt frontend We can build frontend once and publish it. drive-by: roll Chrome DevTools frontend to latest. Fixes #23
Steps to reproduce
Tell us about your environment:
What steps will reproduce the problem?
ndb .
orndb <filename>.js
ndb
does indeed launch, but only shows a black window.What is the expected result?
The proper debugger UI should show up.
What happens instead?
None of the UI renders.
The text was updated successfully, but these errors were encountered: