-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
feat: Added codemods for migrating webpack from v4 to v5 #7388
base: main
Are you sure you want to change the base?
feat: Added codemods for migrating webpack from v4 to v5 #7388
Conversation
@akash-kumar-dev is attempting to deploy a commit to the Webpack Docs Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should add note that this is not an official code mod and might fall short in some cases and that the codemod doesn't guarantee 100% of migration, there may be additional manual steps required.
Thanks for the feedback! I've updated the documentation to clarify that the codemod is unofficial and may require additional manual steps for a complete migration. |
docs: adjust wording
Hi @snitin315 👋 Mohab from Codemod core team here. We reviewed and adjusted this from our end as well. Please let me know if there are any changes you'd like to see. Cheers. |
@mohab-sameh can you sign CLA? |
@snitin315 Should I sign this personally in addition to the one signed by @alexbit-codemod on behalf of Codemod? |
You can sign it personally |
@snitin315 done. Ready to merge now. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@snitin315 Just checking up on this. CLA should be signed. Please let me know if you'd like the core team to make more changes or do final reviews so we can merge this. |
This PR enhances the webpack v5 from v4 migration guide by incorporating codemod integration to streamline the upgrade process for developers. The motivation behind this change is to provide a more efficient and time-saving approach for migrating from v4 to v5, helping the community upgrade with ease.
Key changes include:
By incorporating these changes, the migration guide now provides a more comprehensive and efficient solution for upgrading to webpack v5, helping developers save time and effort during the migration process.