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
Currently, when we bundle a Bun.js server application into an EXE for Windows, this executable cannot function as a proper Windows Service out of the box. The key issue is that the Bun-bundled EXE fails to respond to Windows Service Control Manager (SCM) lifecycle commands (e.g., start, stop, pause, continue, shutdown notifications).
Because of this limitation, we are forced to rely on third-party wrappers to "wrap" the Bun EXE .
Ideas:
Enhance Bun.js's Windows bundling functionality to produce EXEs that are natively service-capable—meaning they can be directly installed and managed via the sc command (no third-party tools required) by:
Adding native support for Windows Service Control Manager (SCM) communication within bundled EXEs, so the application can properly receive and respond to SCM lifecycle commands (start, stop, pause, continue).
Ensuring bundled Bun EXEs comply with Windows service executable requirements, allowing seamless installation via sc create binPath= "" and management via sc start/stop .
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, when we bundle a Bun.js server application into an EXE for Windows, this executable cannot function as a proper Windows Service out of the box. The key issue is that the Bun-bundled EXE fails to respond to Windows Service Control Manager (SCM) lifecycle commands (e.g., start, stop, pause, continue, shutdown notifications).
Because of this limitation, we are forced to rely on third-party wrappers to "wrap" the Bun EXE .
Ideas:
Enhance Bun.js's Windows bundling functionality to produce EXEs that are natively service-capable—meaning they can be directly installed and managed via the sc command (no third-party tools required) by:
Adding native support for Windows Service Control Manager (SCM) communication within bundled EXEs, so the application can properly receive and respond to SCM lifecycle commands (start, stop, pause, continue).
Ensuring bundled Bun EXEs comply with Windows service executable requirements, allowing seamless installation via sc create binPath= "" and management via sc start/stop .
Beta Was this translation helpful? Give feedback.
All reactions