add lock for assets

[atharvadeosthale]

Summary by CodeRabbit

• Chores
  • Implemented caching mechanism for asset optimization to reduce redundant processing and improve overall build efficiency.

[coderabbitai]

Walkthrough

The change introduces a caching mechanism to the asset optimization script that uses SHA256 hashes to track processed files. A persistent cache file (.optimize-lock.json) stores file hashes, enabling the script to skip re-optimization when file content hasn't changed. The implementation includes helper functions for loading and saving the cache, hash computation, tracking of processed files, and cleanup of cache entries for deleted assets. Cache updates are integrated at decision points throughout the optimization loop, and error handling around image processing is enhanced.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'add lock for assets' is directly related to the main change: introducing a caching/locking mechanism for asset optimization via a .optimize-lock.json file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch optimize-lock

---

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