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

Fix Webpack & Browserslist Deprecation Warnings #2269

Conversation

akathedeveloper
Copy link

@akathedeveloper akathedeveloper commented Sep 15, 2024

What kind of change does this PR introduce?

Refactoring and enhancement

Issue Number: #2258

Fixes #

Did you add tests for your changes?

No

Snapshots/Videos:

N/A

If relevant, did you update the documentation?

N/A

Summary

This pull request addresses the deprecation warnings related to Webpack Dev Server in the react-scripts package by updating the configuration in webpack.config.js. Specifically, it replaces the deprecated onBeforeSetupMiddleware and onAfterSetupMiddleware options with the new setupMiddlewares option.

Additionally, a new postinstall script has been added to the package.json file:

Changes Made:

  • Updated Webpack Configuration:
    Replaced onBeforeSetupMiddleware and onAfterSetupMiddleware with setupMiddlewares in webpack.config.js.
  • Added postinstall Script:
    Added "postinstall": "patch-package" to package.json to apply patches automatically.

Testing

  • The changes have been tested locally to ensure that:
  1. The deprecation warnings are resolved.
  2. The postinstall script correctly applies the necessary patches.

Does this PR introduce a breaking change?

NO

Other information

The PR includes a necessary update to the react-scripts package configuration to comply with the latest Webpack Dev Server standards. This change ensures continued compatibility and prevents future issues with deprecated configuration options.

Have you read the contributing guide?

Yes

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Added support for managing patches to dependencies with the patch-package tool.
    • Implemented automatic patch application after dependency installation.
  • Improvements

    • Enhanced middleware setup for the Webpack Dev Server, streamlining the configuration process for better maintainability and clarity.
  • Bug Fixes

    • Improved handling of source maps and path redirection in the development environment.

Copy link

coderabbitai bot commented Sep 15, 2024

Walkthrough

The pull request introduces updates to the package.json file by adding the patch-package dependency and modifying the version specification of react-scripts. A postinstall script is also included to automate patch application. Additionally, the webpackDevServer.config.js file has been refactored to streamline middleware setup by replacing the existing hooks with a consolidated setupMiddlewares function, enhancing the configuration's clarity and maintainability.

Changes

File Change Summary
package.json - Added: "patch-package": "^8.0.0"
- Modified: "react-scripts": "5.0.1""react-scripts": "^5.0.1"
- Added: "postinstall": "patch-package"
patches/react-scripts+5.0.1.patch - Renamed: onBeforeSetupMiddlewaresetupMiddlewares
- Renamed: onAfterSetupMiddleware → incorporated into setupMiddlewares
- Updated middleware setup for Webpack Dev Server to improve clarity and functionality.

Poem

🐰 In the garden where code does play,
New patches bloom, brightening the way.
React scripts dance, with versions to sway,
Middleware sings in a streamlined array.
Hooray for the changes, hip-hip-hooray! 🌼


Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a274353 and 8fe1771.

Files selected for processing (1)
  • patches/react-scripts+5.0.1.patch (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • patches/react-scripts+5.0.1.patch

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 generate interesting stats about this repository and render them as a table.
    -- @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.

Copy link

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

coderabbitai[bot]
coderabbitai bot previously approved these changes Sep 15, 2024
Copy link

codecov bot commented Sep 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.54%. Comparing base (1c641cd) to head (8fe1771).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #2269   +/-   ##
========================================
  Coverage    97.54%   97.54%           
========================================
  Files          241      241           
  Lines         6887     6887           
  Branches      2016     2016           
========================================
  Hits          6718     6718           
  Misses         157      157           
  Partials        12       12           

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

@palisadoes
Copy link
Contributor

Please fix the first comment so that each issue listed automatically closes. The PR_GUIDELINES.md file has details.

Please also fill in the template for the pull request as completely as you can. It greatly helps others searching for code changes in future and helps others understand the summarized rationale for the work you have done

Also make sure the title is easily searchable for terms related to what the PR is about.

Copy link
Contributor

@palisadoes palisadoes left a comment

Choose a reason for hiding this comment

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

Please fix the first comment so that each issue listed automatically closes. The PR_GUIDELINES.md file has details.

Please also fill in the template for the pull request as completely as you can. It greatly helps others searching for code changes in future and helps others understand the summarized rationale for the work you have done

Also make sure the title is easily searchable for terms related to what the PR is about.

@@ -1,11 +1,3 @@
-// @remove-on-eject-begin
-/**
- * Copyright (c) 2015-present, Facebook, Inc.
Copy link
Contributor

Choose a reason for hiding this comment

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

Why have you removed the comments? Others will need to reference this in future and without the context it will be harder.

Copy link
Author

Choose a reason for hiding this comment

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

Sir I have not removed any comments these are the comments that are generated when we install node_modules

Copy link
Author

Choose a reason for hiding this comment

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

I will add comments to the file to make it self-explanatory.

@akathedeveloper akathedeveloper changed the title Update Webpack Configuration and Add Postinstall Script to Address Deprecation Warnings Fix Webpack & Browserslist Deprecation Warnings Sep 15, 2024
@akathedeveloper akathedeveloper deleted the talawa/webpack branch October 13, 2024 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants