refactor: remove unused dependency rimraf

[j9t]

The rimraf package was removed from both the codebase and the package.json dependencies as it is no longer utilized. This change also cleans up related entries in the package-lock.json to maintain consistency.

(This commit message was AI-generated.)

Summary by CodeRabbit

• New Features

  • Updated version to 4.0.6.
  • Enhanced file compression functionality with dynamic command-line argument handling.
  • Added support for compressing staged files based on user-defined patterns.

• Bug Fixes

  • Improved error handling during the retrieval of git status.

• Chores

  • Removed unnecessary dependency on rimraf.

[coderabbitai]

Walkthrough

The pull request introduces modifications to the package.json and src/index.js files. The version number in package.json has been incremented from 4.0.5 to 4.0.6, and the rimraf dependency has been removed. In src/index.js, the script's image compression functionality has been enhanced with improved command-line argument handling, support for staged files via simple-git, and more robust file pattern matching and error handling.

Changes

File	Change Summary
package.json	- Version updated from 4.0.5 to 4.0.6 - Removed rimraf dependency
src/index.js	- Removed rimraf import - Enhanced command-line argument processing with yargs - Added support for staged files using simple-git - Improved file pattern matching with globbySync - Added error handling for git status retrieval

Sequence Diagram

sequenceDiagram
    participant CLI as Command Line
    participant Script as Image Compression Script
    participant Git as Git Repository
    participant Filesystem as Filesystem

    CLI->>Script: Provide arguments
    Script->>Git: Check staged files (if --staged)
    Git-->>Script: Return staged files
    Script->>Filesystem: Find files matching patterns
    Filesystem-->>Script: Return matching files
    Script->>Script: Filter files
    Script->>Script: Compress images
    Script->>CLI: Log compression summary

Loading

The sequence diagram illustrates the enhanced workflow of the image compression script, showing how it now handles command-line arguments, interacts with Git for staged files, finds matching files, and performs compression with improved error handling.

---

📜 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 fb2f08b and 860677e.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/index.js (0 hunks)

💤 Files with no reviewable changes (1)

• src/index.js

🔇 Additional comments (1)

package.json (1)

45-45: LGTM! Version bump follows semver.

The patch version increment (4.0.5 → 4.0.6) is appropriate for removing an unused dependency.

Let's verify the dependency removal and version consistency:

✅ Verification successful

Version bump is consistent and rimraf dependency is properly removed

The verification confirms:

• No usage of rimraf found in the codebase
• Package version (4.0.6) is consistent between package.json and package-lock.json
• No remaining imports or requires of rimraf

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify rimraf removal and version consistency

# Check if rimraf is still used anywhere in the codebase
echo "Checking for rimraf usage..."
rg -l 'rimraf'

# Check if package-lock.json version matches
echo "Checking version consistency..."
if [ -f "package-lock.json" ]; then
  jq -r '.version' package-lock.json
fi

# Verify no direct imports of rimraf remain
echo "Checking for rimraf imports..."
ast-grep --pattern 'import $_ from "rimraf"'
ast-grep --pattern 'require("rimraf")'

Length of output: 385

---

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.

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.