chore(amplify): update Node version in package.json and streamline am…

[Stivenjs]

…plify.yml

This commit updates the Node version in package.json to 22.12.0 and removes unnecessary preBuild commands from amplify.yml, simplifying the build process while ensuring compatibility with the specified Node version.

Summary by CodeRabbit

• Chores
  • Updated configuration to specify the required Node.js version for the project.
  • Simplified build process by removing pre-build steps related to Node.js version management.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes remove Node.js version management and npm install steps from the preBuild phases in both backend and frontend sections of amplify.yml. Additionally, a Node.js version requirement is specified in the package.json using the engines field. No other configurations or scripts were altered.

Changes

File(s)	Change Summary
amplify.yml	Removed preBuild steps for Node.js version management and npm install in backend/frontend.
package.json	Added "engines": { "node": "22.12.0" } to specify required Node.js version.

Possibly related PRs

• chore(amplify): remove unnecessary preBuild commands in amplify.yml #70: Also removes the preBuild phase and Node.js version management commands from amplify.yml.
• chore(amplify): add Node version management and npm installation in p… #73: Previously added the preBuild Node.js steps and a prepare script; this PR effectively reverts those changes.

Poem

A hop and a skip, the scripts are now lean,
No more preBuild steps to be seen!
Node's version is locked, in engines it stays,
Amplify builds in more streamlined ways.
With a twitch of my nose and a satisfied cheer,
The code is now simpler—let’s all give a bunny ear! 🐰

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a96e736 and 47c33d6.

📒 Files selected for processing (2)

• amplify.yml (2 hunks)
• package.json (1 hunks)

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.