Add example with Node bundled about socket-examples HOT 9 CLOSED

@chicoxyzzy I'll assign you here to this so you can close this when you have an example app for this particular use case

from socket-examples.

see socketsupply/socket#3

Looks like a different error actually

from socket-examples.

I don't think that's related, @nichoth. This isn't a Bluetooth permission issue. And I don't get a crash report window like that issue does.

from socket-examples.

So the app works as expected when I use open dist/mac/TestExample-dev.app in the terminal. But when I open it by double-clicking from the Finder, this bug appears.

from socket-examples.

I can confirm the app crashes on button click when it's opened from the Finder. Updates from the Node backed doesn't seem to work as well

from socket-examples.

The issue is that the node command cannot be resolved when running from Finder (double clicking the .app file) because there the PATH env var is very limited by default (/usr/bin:/bin:/usr/sbin:/sbin)

node is available on my PATH in /usr/local/bin so changing the mac_cmd to

mac_cmd: /usr/local/bin/node index.js

fixes this and prevents a crash

it is unfortunate that we have no crash report or logs for things like this

from socket-examples.

Shouldn't node be included in the .app so end users don't need to install Node themselves?

from socket-examples.

error logs could be caught via

window.addEventListener('process-error', ({ detail }) => {
  console.error('process-error', detail)
})

in the frontend code. Hm, maybe we should add this to the preload script.

from socket-examples.

Shouldn't node be included in the .app so end users don't need to install Node themselves?

it is definitely possible and that's how our own apps work. That will make example apps code a bit more complicated. I think that we should rethink example apps to make some of them work without node and make others use bundled node. @heapwolf @jwerle WDYT?

from socket-examples.