fix: prod start issue - #71
Merged
Merged
Conversation
chaitanyapotti
approved these changes
Mar 11, 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.
Motivation and Context
Jira Link:
NA
Description
Fix build issue on prod after stack upgrade
How has this been tested?
Screenshots (if appropriate):
Types of changes
Checklist:
Note
Medium Risk
Touches production boot/migration scripts and DB connection configuration (read/write splitting and Aurora session settings), which can cause runtime or connectivity issues if environment variables/configs are mismatched.
Overview
Fixes production startup by separating dev vs prod execution:
startnow runs TypeScript viatsx, whileprodruns the compileddistoutput, and Knex migration scripts are adjusted to run TypeScript configs under newer Node (NODE_OPTIONS='--import tsx').Updates database bootstrapping to explicitly select read/write Knex configs based on
NODE_ENV(development/staging/production) and adds an Aurora read-replicaafterCreatehook plus connection logging inknexfile.tsto ensure expected session consistency settings in replica environments.Written by Cursor Bugbot for commit e5b1ea3. This will update automatically on new commits. Configure here.