fix: updated eslint version

[Aryan4884]

What kind of change does this PR introduce?
Bugfix

Issue Number:

Fixes #2518

Did you add tests for your changes?

No

Snapshots/Videos:

N/A

Summary

This pull request updates the Mongoose version from 8.3.2 to 8.7.0

Does this PR introduce a breaking change?

No, the update does not introduce any breaking changes.

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• Chores
  • Updated eslint package to improve code quality tools.
  • Added new dependency cls-bluebird for enhanced functionality.
  • Specified compatibility for graphql version in graphql-voyager.

[coderabbitai]

Walkthrough

The changes in the pull request primarily involve updates to the package.json file for the talawa-api project. Key modifications include upgrading the eslint package from version ^8.56.0 to ^9.10.0, adding a new dependency cls-bluebird at version ^2.1.0, and setting an override for the graphql dependency used by graphql-voyager. The lint-staged configuration remains unchanged.

Changes

File	Change Summary
package.json	- Updated eslint from ^8.56.0 to ^9.10.0
	- Added cls-bluebird at version ^2.1.0 in devDependencies
	- Added override for graphql in graphql-voyager to ^16.6.0

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade the eslint package from version 8.57.0 to 9.10.0 (#2518)	✅
Address issues that caused previous automated attempts to fail (#2518)	❌	No evidence of addressing previous failures.
Update multiple files to accommodate changes in syntax (#2518)	❓	Changes to files beyond package.json unclear.
Ensure compatibility with the new version (#2518)	✅

Possibly related issues

• Upgrade package mongoose from 8.3.2 to 8.4.4 #2323: This issue involves upgrading the mongoose package, which may relate to dependency management, similar to the updates made in this PR.

Possibly related PRs

• Migrating to eslint.config.js #2522: This PR involves changes to the package.json file related to ESLint configuration, directly connecting to the main PR's update of the eslint package version.
• Upgraded the nodemailer package to 6.9.15 #2549: This PR updates a dependency in the package.json file for the nodemailer package, indicating a similar type of change in dependency management.

Suggested reviewers

• varshith257
• palisadoes

Poem

In the code where rabbits hop,
Dependencies rise and never stop.
ESLint's new, with rules so bright,
Cls-bluebird joins the coding fight.
With every change, we leap with glee,
For cleaner code, oh joy, oh me! 🐇✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c1dc667 and 8499ee4.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (1 hunks)

🧰 Additional context used

🔇 Additional comments (4)

package.json (4)

Line range hint 1-165: Summary of package.json changes

1. The eslint update to version ^9.10.0 aligns with the PR objectives.
2. The addition of cls-bluebird and the graphql-voyager override require further explanation as they don't directly relate to the eslint update.
3. Given that this is a major version update for eslint, it's crucial to verify that all existing lint rules are still compatible and that no new errors or warnings have been introduced.

Please provide clarification on the additional changes and ensure that comprehensive testing is performed to validate the eslint update across the entire codebase.

---

Line range hint 151-155: Clarify the addition of graphql-voyager override

The addition of an override for graphql-voyager, specifying graphql version ^16.6.0, doesn't seem directly related to the eslint update. Could you please explain why this override is necessary?

#!/bin/bash
# Check for any conflicts or issues related to graphql versions
npm ls graphql

# Check if graphql-voyager is used in the project
rg --type typescript 'graphql-voyager'

---

135-135: Clarify the addition of cls-bluebird dependency

The addition of cls-bluebird as a dev dependency doesn't seem to be related to the eslint update mentioned in the PR objectives. Could you please explain why this library is being added and how it relates to the current changes?

---

136-136: Approve eslint update and verify compatibility

The update of eslint to version ^9.10.0 aligns with the PR objectives and goes beyond the version mentioned in the linked issue. This is a major version update, which may introduce breaking changes.

Please run the following commands to verify compatibility and identify any necessary adjustments:

---

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

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.

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.58%. Comparing base (c1dc667) to head (8499ee4).
Report is 3 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2594   +/-   ##
========================================
  Coverage    98.58%   98.58%           
========================================
  Files          356      356           
  Lines        18061    18061           
  Branches      2411     2411           
========================================
  Hits         17806    17806           
  Misses         252      252           
  Partials         3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.