Results 381 comments of Cas_

yeah using electron-rebuild works, as I said [here](https://github.com/animetosho/node-yencode/pull/15#issuecomment-3386654338), I'm running the library inside a utilityProcess, which is likely why electron shits itself and doesn't print a stack trace it's likely...

this lib also doesn't compile correctly for macOS on arm64, you end up with a `error: unknown target CPU 'apple-m3'` caused by `-march=native` adding ``` ['OS=="mac" and enable_native_tuning!=0', { "conditions":...

as mentioned here https://github.com/animetosho/node-yencode/pull/15#issuecomment-3388679340 without one of those 3 libs in Dev dependencies the developer needs to manually rebuild the package because electron-builder won't detect it as native and won't...

I'll update this PR with fixes you should be satisfied with tomorrow

> If I take https://github.com/animetosho/node-yencode/pull/15#issuecomment-3392986108, delete the yencode build and add yencode as a dependency in package.json, issuing a npx electron-rebuild does cause yencode to be rebuilt. This suggests that...

god, this entire thing is making me look inept, but at least I have workflow logs to back me up [1](https://github.com/hayase-app/electron/actions/runs/18435274654/job/52527900559#step:9:395), so it's odd it didn't happen for you

yeah that doesn't seem to have fixed it: https://github.com/hayase-app/electron/actions/runs/18466506240/job/52609666071#step:9:395

[nope](https://github.com/hayase-app/electron/actions/runs/18525820952/job/52796287906#step:9:395)

VERY weird that the issue doesn't occur when I do this: https://github.com/animetosho/node-yencode/pull/15#issuecomment-3393741369 also compiles it for the correct arches

it really doesnt matter, its called twice, maybe 3 times, only during testing