Best posts made by axellejamous

Solved the issue by simply running npm install in the vendor folder.

Found thanks to this issue

Thought I’d share the solution so maybe noobs like me can use it in the future.

@Mykle1
I did luckily!
I indeed had the issue after manual installation. Fact is, the automatic installation script would actually get stuck on two of my Pi’s at the node modules installation.
So I had to manually install.

In the issue that helped me find the answer, he did do a manual install as well and had the same problem.
But someone did mention “in the latest version there is a npm install task in the vendor folder as well which gets executed automatically after a successful install, yours wasn’t successful so this was never executed” which means I probably made a mistake in my manual installation, although I have no clue what it could’ve is as I followed the steps thoroughly on 2 different pi’s, getting the same result.

@bhepler I was! But I manages to fix the issue.
When checking npm versions I saw that electron was ver 1.8.1
I ended up rolling back to 1.7.9 and it works perfectly!
Have no idea why 1.8.1 results in a black screen though.

@Mykle1 this was indeed the alternative solution I had in mind! I managed to get it to work now, but it looks a bit iffy since both instances of the module will receive the incoming data and so it will be displayed on the screen twice (which doesn’t seem to happen with outgoing data). I’m going to try see if I can manage to display it only on one of them and otherwise I’ll revert to the alternative you suggested! Thank you :)

@Mykle1 I ended up copying and renaming the entire module! Worked way better than my silly workaround. Thank you! :)