add patches file to docker file

[tsimsekburgan]

Summary by CodeRabbit

• Chores
  • Improved Docker build configuration to enhance dependency management during the installation process.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: de9d6284-04d4-422a-8cfc-91825b17d1f7

📥 Commits

Reviewing files that changed from the base of the PR and between e38ee27 and bcea145.

📒 Files selected for processing (1)

• Dockerfile

---

📝 Walkthrough

Walkthrough

The Dockerfile is modified to copy a patches directory into the builder image before running npm ci. This single-line addition enables patch files to be accessible during the dependency installation phase.

Changes

Docker patch file support

Layer / File(s)	Summary
Patch files in builder stage Dockerfile	The COPY patches ./patches instruction is added to the builder stage before npm ci runs, ensuring patch files are available during dependency installation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A patch here, a patch there,
In Docker's layers, with builder care,
Before npm installs each precious tome,
The patches hop into their new home!
One line of copy, so small and neat,
Makes dependency patches complete. ✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sprint9-26/Ui

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the Dockerfile to include a patches directory during the build process, ensuring that local patches are available for npm ci. A review comment suggests using trailing slashes in the COPY command to explicitly define the source and destination as directories, which is a best practice for clarity and error prevention.

[gemini-code-assist]

While COPY patches ./patches works for directories, it is a best practice to use trailing slashes when copying directories in a Dockerfile. This explicitly signals to Docker that the destination should be a directory and helps prevent issues if the source is unexpectedly a file.

COPY patches/ ./patches/