-
Notifications
You must be signed in to change notification settings - Fork 267
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Ensure socket messages are always sent for all npm installs (#419)
* feat: hide the installation toast when a server driven npm install finishes * feat: ensure the first and second npm install when creating an ai app are properly sequenced, and that the process gets deleted at the end * feat: send more websocket messages to make sure the client always knows about in flight npm installs * feat: send a socket message on connection that relays the current npm install status * feat: always listen for deps:status messages and keep the usePackageJson context up to date * feat: add mechanism to automatically broadcast deps:* messages whenever dependencies are installed Previously, events were sent bespoke in each implementation. Many missed events and that led to cases where the client often had no idea the state of the server. Now, always send all events always. * fix: add missed `onExit` handler * fix: run npm run format * fix: address linter warning * feat: wrap all returns coming out of npmInstall in waitForProcessToComplete * fix: modify wss.onJoin to take the standard set of parameters as other handler functions
Showing
7 changed files
with
147 additions
and
77 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters