-
Notifications
You must be signed in to change notification settings - Fork 10.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
fix(gatsby-plugin-netlify): upgrade webpack-assets-manifest for compatibility with webpack@5 #30217
fix(gatsby-plugin-netlify): upgrade webpack-assets-manifest for compatibility with webpack@5 #30217
Conversation
@pedrolamas - did you run
I guess what I'm trying to say is, you can't just upgrade |
@kimbaudi I did indeed, it passed perfectly on my end (tested under Windows 10)! |
@pedrolamas - I just tested after upgrading to |
@kimbaudi Can I ask you to checkout my branch, run |
@pedrolamas - ok I'll check out your branch and give it a shot. btw, you can shorten the command to |
Sorry @kimbaudi, I'm not a big git cli user, so I'm just copying the commands from Git Extensions! 😁 |
@pedrolamas - I tested on your branch (and on my fork as well) and it works. I guess I did something wrong earlier. sorry about that |
…-plugin-netlify-update
For the record, I've tested this change locally with yalc and it worked fine for me (error messages are gone). |
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.
Thanks!
I just upgraded Gatsby to |
Never mind - fixed by running |
Description
Some deprecation errors are showing from
gatsby build
whengatsby-plugin-netlify
is in use, this fixes the problem by upgrading thewebpack-assets-manifest
version to the same used in the rest of gatsby codebase.Related Issues
Fixes #29974