chore: remove unnecessary lint-staged config and dependency

[G4URAV001]

fixes PSMRI/AMRIT#98

Description
Removed unnecessary lint-staged configuration and dependency from the project. The lint-staged configuration was targeting TypeScript, CSS, and HTML files in the src directory, but none of these file types exist in the repository as it's a Java-based project. Also removed the pre-commit Git hook that was using lint-staged since it's no longer needed.

Changes made:

• Removed the lint-staged configuration from package.json
• Removed the lint-staged dependency from package.json
• Removed the pre-commit hook from .husky directory
• Updated package-lock.json by running npm install

These changes help clean up the project by removing unused configurations and dependencies, making the repository more maintainable.

Type of change

• Bug fix
• New feature
• Enhancement
• Refactoring
• Documentation
• Other ( please specify )

How Has This Been Tested?
The changes have been verified by:

• Confirming no TypeScript, CSS, or HTML files exist in the src directory
• Verifying that the package.json and package-lock.json files are valid after removing the dependency
• Confirming that npm install runs successfully after the changes

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

• Chores
  • Removed lint-staged integration and related configuration from the project.
  • Deleted the pre-commit hook that previously ran lint-staged.

[coderabbitai]

Walkthrough

This change removes the project's usage of lint-staged by deleting its configuration and dependency from package.json and eliminating the .husky/pre-commit file that previously invoked lint-staged before commits. No other configurations or exported entities are altered.

Changes

File(s)	Change Summary
.husky/pre-commit	Deleted the pre-commit hook that ran npx lint-staged.
package.json	Removed the lint-staged configuration and the lint-staged package from devDependencies.

Possibly related issues

• Remove Unused lint-staged Configuration for Non-Existing ts and css Files AMRIT#98: The changes remove .husky/pre-commit and all lint-staged references, directly addressing the issue's objective.

Poem

A rabbit hopped through code so neat,
Swept away lint-staged from under its feet.
No more pre-commit to slow the flow,
Just pure commits, ready to go!
With a twitch of the nose and a satisfied grin,
The repo is lighter—let coding begin!
🐇✨

---

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

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

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)

package.json (1)

15-21: DevDependencies cleanup complete
The lint-staged devDependency has been removed successfully, and there’s no leftover lint-staged configuration. Please verify that package-lock.json was regenerated accordingly and that CI passes without any lint-staged references.
If you’ve removed all Husky hooks (e.g., .husky/pre-commit), you may also consider removing the "prepare": "husky" script and the husky devDependency to fully clean up the repository.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bf084a1 and af0959f.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• .husky/pre-commit (0 hunks)
• package.json (1 hunks)

💤 Files with no reviewable changes (1)

• .husky/pre-commit

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[G4URAV001]

cc: @drtechie