You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not running native code on the Electron browser process to allow locking it down more in the future
Note that the node-pty repo and npm package will remain, nothing will change in that respect. The node-pty repo and package will mainly just be glue code between the new sub-components.
The text was updated successfully, but these errors were encountered:
@Tyriar Sounds reasonable. All it needs on C++ side to keep ptys alive under Unix is the valid pty master fd (plus the emulator and buffer states to continue exactly where it stopped). Only the raw pty creation needs to be in component one, the shell could be spawned in TS land. No clue if such a separation would work with winpty.
I'm proposing we split node-pty into 2 sub-components that can be used independently or together with node-pty. The components would do:
This will help support:
Note that the node-pty repo and npm package will remain, nothing will change in that respect. The node-pty repo and package will mainly just be glue code between the new sub-components.
The text was updated successfully, but these errors were encountered: