chore: Enable source maps for RTS for better error traces

[sharat87]

Description

The source maps files are there in the RTS folder but aren't being used because they aren't enabled. This PR fixes that by adding the necessary option to node to get better stack traces that point to the actual TypeScript files.

Automation

/test sanity

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Chores
  • Updated the server runtime to improve error reporting and debugging, resulting in more detailed and readable error traces for a smoother troubleshooting experience.

[coderabbitai]

Walkthrough

The pull request updates the run-rts.sh script by modifying the Node.js execution command to include the --enable-source-maps flag. This change enhances debugging and error reporting capabilities by providing source map support when running the Node.js server.

Changes

File(s)	Change Summary
deploy/docker/.../run-rts.sh	Modified the Node.js execution command to include the --enable-source-maps flag

Possibly related PRs

• chore: move the rts.conf code to shell file #38859: Modifies the execution command in the same run-rts.sh script, establishing a direct connection.
• chore: disable sourcemaps for non-prod builds and cleanup craco configs #38706: Involves source map configuration changes that are related to enabling source map support in the Node.js runtime.

Suggested labels

skip-changelog, ok-to-test

Suggested reviewers

• pratapaprasanna

Poem

In the shell where code takes flight,
A flag now guides the debug light.
Source maps now show the way,
Unraveling bugs come what may.
Cheers to smoother runs and brighter nights!

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8314a30 and 1394958.

📒 Files selected for processing (1)

• deploy/docker/fs/opt/appsmith/run-rts.sh (1 hunks)

🔇 Additional comments (1)

deploy/docker/fs/opt/appsmith/run-rts.sh (1)

3-3: Enable Source Maps for Enhanced Debugging

The updated command now includes the --enable-source-maps flag, which directly addresses the PR objective by improving stack trace readability during error handling. Please ensure that the Node.js version in use supports this flag.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.