chore: Remove PM2 from EB startup [WPB-23932]#20630
Merged
thisisamir98 merged 2 commits intodevfrom Mar 10, 2026
Merged
Conversation
zskhan
previously approved these changes
Mar 10, 2026
Let Elastic Beanstalk manage the web process directly by starting the server with node instead of PM2. This removes an unnecessary runtime dependency, avoids missing PM2 binary failures during deployment, and prevents conflicts with EB PID tracking and restart handling.
Contributor
|
🔗 Download Full Report Artifact 🧪 Playwright Test Summary
|
Add tslib to apps/server/package.json because the compiled server output requires it at runtime when importHelpers is enabled. This fixes Elastic Beanstalk startup failures caused by: Error: Cannot find module 'tslib'
|
zskhan
approved these changes
Mar 10, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Let Elastic Beanstalk manage the web process directly by starting the server with node instead of PM2.
This removes an unnecessary runtime dependency, avoids missing PM2 binary failures during deployment, and prevents conflicts with EB PID tracking and restart handling.