MacOS: A Javascript error occurred in the main process

[shaunsingh]

Built on M1 (macOS, arm64). Latest NPM/Yarn. Just cloned it today, built from master with npm ci then npm run package

[smolck]

Quick sanity check, this commit isn’t what caused this right? Still broken before that?

[shaunsingh]

I just tried building it on the release commit: https://github.com/smolck/uivonim/tree/a335d9207cd3e227604f22c58ffdfd02f0e07531 and it gives the same error

[clason]

Does it work if you run npm run prod?

(I've been checking the dependabot bumps on my Mac routinely and don't get this error.)

[smolck]

I can reproduce this; it only seems to happen with the macOS uivonim.app though.

While I don't know why it's happening only with the uivonim.app (maybe macOS sandboxing or something?), it seems to be yet another issue occurring from connecting to neovim separately from the nvim process child stdin/stdout (which is used exclusively for UI event stuff, at least afaik). This separate connection was apparently done for a potential performance improvement, but it adds a good deal of complication to the codebase, and the benefit is quite possibly little to none. So my plan to fix this (and the WSL issue too, hopefully) is to just use the nvim child stdin/stdout communication for everything.

[Pritep]

Me too, but on Linux.

[advnpzn]

I get the same error and I'm on windows 10 22H2.