Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Fixed Node Warning and Deprecation Messages #3262

Open
wants to merge 2 commits into
base: develop-postgres
Choose a base branch
from

Conversation

abbi4code
Copy link
Contributor

@abbi4code abbi4code commented Jan 12, 2025

What kind of change does this PR introduce?
This pr fixes Node Warning and Deprecation Messages When Installing App Packages.

Issue Number:

Fixes #3167

Snapshots/Videos:

  • Before

400261071-8ddf10af-8095-4dff-967c-81463c0bcc08

  • After

Screenshot from 2025-01-12 21-19-14

Explaination
Screenshot from 2025-01-12 21-24-34

  • "overrides": { "rc-color-picker": { "react": "^18.3.1", "react-dom": "^18.3.1" }, },

  • Added rc-color-picker to overrides to resolve peer dependency conflicts. The package normally requires React 16.x, but our project uses React 18.3.1. This override ensures rc-color-picker uses the correct React version, preventing potential compatibility issues and dependency warnings.

  • Many packages in our dependency chain rely on deprecated versions of their sub-dependencies
    Like
    Screenshot from 2025-01-12 21-30-08
    Screenshot from 2025-01-12 21-30-29

  • "core-js": "^3.40.0" this will enforce all instances of core-js in the dependency tree to use version 3.40.0 and so on.

Regarding other depreciated msg
Screenshot from 2025-01-12 21-40-58

  • we can solve this by install latest eslint package ie 9.10.0

Summary by CodeRabbit

  • Dependency Management
    • Removed development dependencies for type definitions
    • Added package version overrides to ensure compatibility
    • Updated core library and package constraints

Copy link
Contributor

coderabbitai bot commented Jan 12, 2025

Walkthrough

The pull request involves modifications to the package.json file, focusing on dependency management. Two development dependencies (@types/react-chartjs-2 and @types/react-datepicker) have been removed, and a new "overrides" section has been introduced. This section specifies version constraints for packages like core-js, rc-color-picker, and gulp-header, aiming to address potential compatibility and warning issues during package installation.

Changes

File Change Summary
package.json - Removed @types/react-chartjs-2 from devDependencies
- Removed @types/react-datepicker from devDependencies
- Added overrides section with version constraints for core-js, rc-color-picker, and gulp-header

Assessment against linked issues

Objective Addressed Explanation
Fix Node Warning and Deprecation Messages [#3167]
Correctly update packages to remove console errors
Ensure valid fix without hiding messages

Possibly related issues

Possibly related PRs

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

  • palisadoes

Poem

🐰 Dependency dance, a package's delight,
Overrides and constraints, making versions right!
Warnings fade away, like rabbits in flight,
Clean dependencies sparkle, oh so bright! 🎉


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

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.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (2)
package.json (2)

Line range hint 23-23: Restore type definitions for react-chartjs-2 and react-datepicker

The packages react-chartjs-2 and react-datepicker are present in dependencies but their TypeScript type definitions have been removed. This could cause TypeScript compilation issues.

Please restore the following devDependencies:

 "devDependencies": {
+  "@types/react-chartjs-2": "^5.2.0",
+  "@types/react-datepicker": "^7.5.0",
   ...
 }

Also applies to: 44-44


Line range hint 164-169: Update React types in resolutions section

The resolutions section specifies React types v17.0.2 which conflicts with the project's React v18.3.1. This could lead to type mismatches and incorrect type checking.

Update the resolutions to match the project's React version:

 "resolutions": {
   "@apollo/client": "^3.4.0-beta.19",
-  "@types/react": "17.0.2",
-  "@types/react-dom": "17.0.2",
+  "@types/react": "^18.3.12",
+  "@types/react-dom": "^18.3.1",
   "graphql": "^16.5.0"
 }
🧹 Nitpick comments (1)
package.json (1)

Line range hint 134-138: Align TypeScript-related package versions

There are version mismatches in TypeScript-related packages:

  • @typescript-eslint/eslint-plugin: ^8.11.0
  • @typescript-eslint/parser: ^8.5.0

Consider aligning these versions to ensure compatibility and prevent potential issues.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 018155d and 3c5d57c.

⛔ 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)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Test Application
  • GitHub Check: Analyse Code With CodeQL (javascript)
🔇 Additional comments (2)
package.json (2)

171-178: LGTM! Overrides section properly addresses dependency conflicts

The overrides section correctly:

  • Forces core-js to v3.40.0 to resolve deprecation warnings
  • Aligns rc-color-picker's React dependencies with the project's React version (18.3.1)
  • Sets gulp-header to a stable version

Line range hint 134-135: Update ESLint as mentioned in PR objectives

The PR objectives mention updating ESLint to v9.10.0, but it's currently at v8.49.0.

Please verify if the ESLint update is still needed:

Copy link

codecov bot commented Jan 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.27%. Comparing base (e3a2bdf) to head (b215ba6).
Report is 4 commits behind head on develop-postgres.

Additional details and impacted files
@@                  Coverage Diff                  @@
##           develop-postgres    #3262       +/-   ##
=====================================================
+ Coverage              8.51%   90.27%   +81.75%     
=====================================================
  Files                   309      330       +21     
  Lines                  7811     8491      +680     
  Branches               1730     1875      +145     
=====================================================
+ Hits                    665     7665     +7000     
+ Misses                 7072      598     -6474     
- Partials                 74      228      +154     

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

@palisadoes palisadoes added the ignore-sensitive-files-pr The contributor has a legitimate reason for editiing protected files label Jan 12, 2025
@palisadoes
Copy link
Contributor

Please make a minor commit so that Coderabbit approves

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ignore-sensitive-files-pr The contributor has a legitimate reason for editiing protected files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants