chore: updated all dependencies to the latest version

[Anurag-Wednesday]

Ticket Link

---

Related Links

---

Description

---

Updated all the dependencies to the latest version. Updated eslint config to comply with the newer version

Steps to Reproduce / Test

---

---

Checklist

• PR description included
• yarn test passes
• Tests are [changed or added]
• Relevant documentation is changed or added (and PR referenced)

GIF's

---

Summary by CodeRabbit

• New Features

  • Introduced a comprehensive ESLint configuration to improve code quality and consistency across JavaScript and TypeScript projects.
  • Updated linting scripts in the project for broader linting capabilities.

• Bug Fixes

  • Enhanced error handling in the ErrorBoundary component by enforcing console error logging standards.

• Style

  • Improved readability of JSX in multiple components, including CustomCard and WithAllProviders.
  • Adjusted import order in index.tsx for better clarity and organization.

• Chores

  • Updated various dependencies to their latest versions for improved performance and new features.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
next-bulletproof-ts	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 28, 2024 7:59am

[coderabbitai]

Walkthrough

The changes involve the introduction of a new ESLint configuration file, updates to the package.json for scripts and dependencies, and various modifications across several component files. These modifications include adjustments for code readability, adherence to linting standards, and enhancements in type safety. Overall, the updates aim to maintain a well-structured and modern codebase for improved development practices.

Changes

Files	Change Summary
eslint.config.mjs	New ESLint configuration file established for JavaScript and TypeScript projects, specifying linting rules, global variables, and file types to be linted, along with ignored patterns.
package.json	Updates to scripts for linting and numerous dependency upgrades, including major libraries like React, Next.js, and TypeScript, reflecting a shift in tooling and versioning.
src/common/ErrorBoundary/index.tsx	Removed ESLint directive disabling console error logging, now logging errors directly in adherence to coding standards.
src/common/For/index.tsx	Updated generic type declaration for ForProps for enhanced type safety.
src/common/Loader/tests/index.test.tsx	Modified string delimiters from single to double quotes for consistency in test file.
src/containers/Repos/index.tsx	Reformatted object return structure for improved readability without changing logic.
src/features/repos/components/ErrorState/index.tsx	Restructured JSX for CustomCard for better readability, no change in logic.
src/pages/index.tsx	Reordered import statements for clarity, maintaining original functionality.
src/utils/createEmotionCache.ts	Removed unnecessary blank line for formatting cleanup.
src/utils/index.ts	Adjusted indentation for mapKeysDeep function for better readability and removed a commented-out ESLint directive.
src/utils/testUtils.tsx	Streamlined JSX structure in WithAllProviders component for improved readability without altering functionality.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Component
    participant ErrorBoundary
    participant Loader

    User->>Component: Triggers action
    Component->>ErrorBoundary: Catches error
    ErrorBoundary->>Loader: Displays loading state
    Loader->>User: Shows error message

Loading

🐇 In the code we hop and play,
With linting rules to light the way!
Upgraded tools, dependencies too,
Our project shines, fresh and new!
Through changes big, we dance with glee,
A happy codebase, wild and free! 🌟

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e0c1aac and a33ae94.

Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

Files selected for processing (11)

• eslint.config.mjs (1 hunks)
• package.json (2 hunks)
• src/common/ErrorBoundary/index.tsx (1 hunks)
• src/common/For/index.tsx (1 hunks)
• src/common/Loader/tests/index.test.tsx (1 hunks)
• src/containers/Repos/index.tsx (1 hunks)
• src/features/repos/components/ErrorState/index.tsx (1 hunks)
• src/pages/index.tsx (1 hunks)
• src/utils/createEmotionCache.ts (1 hunks)
• src/utils/index.ts (2 hunks)
• src/utils/testUtils.tsx (1 hunks)

Files skipped from review due to trivial changes (8)

• src/common/ErrorBoundary/index.tsx
• src/common/For/index.tsx
• src/common/Loader/tests/index.test.tsx
• src/containers/Repos/index.tsx
• src/features/repos/components/ErrorState/index.tsx
• src/pages/index.tsx
• src/utils/createEmotionCache.ts
• src/utils/testUtils.tsx

Additional context used

GitHub Check: Build & Lint (20.x)

src/utils/index.ts

[warning] 10-10:
Variable Assigned to Object Injection Sink

---

[warning] 11-11:
Generic Object Injection Sink

Additional comments not posted (3)

eslint.config.mjs (1)

1-35: Comprehensive ESLint Configuration

The configuration file is well-structured and covers a broad spectrum of JavaScript and TypeScript development concerns, including standard JS practices, React-specific rules, security enhancements, and code formatting with Prettier. This setup should significantly aid in maintaining code quality across the project.

The ESLint configuration is appropriate and follows common best practices in modern JavaScript projects.

src/utils/index.ts (1)

8-14: Improved Formatting for Better Readability

The changes in the mapKeysDeep function enhance readability by making the nested structure more visually distinct. This is crucial for maintaining the code easily.

The formatting changes are beneficial and align with best practices for code readability.

Tools

GitHub Check: Build & Lint (20.x)

[warning] 10-10:
Variable Assigned to Object Injection Sink

---

[warning] 11-11:
Generic Object Injection Sink

package.json (1)

8-15: Updated Scripts and Dependencies

The updates to the scripts simplify their usage and make the linting process more robust. The updates to dependencies and devDependencies ensure the project is up-to-date with the latest versions, which can improve security and performance.

The changes to the package.json are well-executed and reflect a proactive approach to maintain the project's dependencies and streamline the development workflow.

Also applies to: 24-101