chore(amplify): simplify npm ci command and remove husky scripts

[Stivenjs]

This commit modifies the npm ci command to exclude development dependencies and removes husky setup scripts from package.json, streamlining the build process for production environments.

Summary by CodeRabbit

• Chores
  • Updated build configuration to simplify dependency installation and remove unnecessary setup steps.
  • Removed unused scripts related to development tooling from the project configuration.

[coderabbitai]

Walkthrough

The updates remove conditional Husky setup commands from both the build pipeline configuration and the npm scripts in package.json. Additionally, the npm install command in the build process no longer explicitly includes development dependencies. No changes were made to exported or public entities.

Changes

File(s)	Change Summary
amplify.yml	Removed "Skipping husky setup in production" echo and simplified npm ci by dropping --include=dev.
package.json	Removed conditional prepare and postinstall Husky setup scripts.

Possibly related PRs

• Templates engine #68: Removes the conditional Husky scripts and the explicit --include=dev flag from npm ci, directly reversing previous additions.

Poem

The scripts are now clean, Husky’s gone from the scene,
No more echoes in build, or dev flags to glean.
With npm ci simple, the process runs light—
The bunny hops forward, the pipeline feels right!
🐇✨

---

🪧 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

amplify.yml (1)

18-18: Ensure dev dependencies are omitted and caching is consistent
The npm ci invocation now lacks both the --omit=dev (or --production) flag—meaning dev deps may still be installed unless NODE_ENV=production—and the cache options used in the backend preBuild. Confirm this is intentional. For clearer intent and faster builds, consider:

-        - npm ci 
+        - npm ci --omit=dev --cache .npm --prefer-offline

Also remove the trailing space at the end of the original line.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 18-18: trailing spaces

(trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e2ee2b6 and 075a107.

📒 Files selected for processing (2)

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

💤 Files with no reviewable changes (1)

• package.json

🧰 Additional context used

🪛 YAMLlint (1.37.1)

amplify.yml

[error] 18-18: trailing spaces

(trailing-spaces)