Packaging with Electron

[Armaldio]

Hey there,

Trying to use your fork in an Electron app
Using pnpm, electron, electron forge

Public repo: https://github.com/CynToolkit/pipelab

When in development, everything works fine
But after being compiled using electron forge, it seems the binaries can't be found

The @lydell/node-pty package supports your platform (win32-x64), but it could not find the binary package for it: @lydell/node-pty-win32-x64/conpty.node

This can happen if you use the "--omit=optional" (or "--no-optional") npm flag.
The "optionalDependencies" package.json feature is used to install the correct
binary executable for your current platform. Remove that flag to use @lydell/node-pty.

This can also happen if the "node_modules" folder was copied between two operating systems
that need different binaries - including "virtual" operating systems like Docker and WSL.
If so, try installing with npm rather than copying "node_modules".

Any idea to point in the right direction ?

Thanks

[lydell]

Hi! I’m sorry, I have never built anything with Electron, so I unfortunately have no clue why that happens. But I’d be open to a pull request that fixes things for Electron!

[kilotone]

I've solved something similar in a few different ways using this package over the last few years.
I think current solution is just making sure that if you are using asar (a virtual file system) that you exclude the contents of the @lydell workspace from being packed, or transpile the exec calls when building. Edit the files setting in builder config target to exclude all of its folder in node modules with glob.

I believe" under asarUnpack /node_modules/@lydell//*",

https://www.electronjs.org/docs/latest/tutorial/asar-archives