-
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-manifest): fixes icons not getting asset prefix #20142
Conversation
b2baa48
to
59067b3
Compare
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.
Some end-to-end tests break on ASSET_PREFIX, I wonder if you could fix them.
So what's the fix? Do i just need to set an empty string if the global isn't already set? If that's the case it seems like this should be handled by What's the "correct" path here? Thanks. |
withPrefix helpers are only accessible in webpack land so gatsby-ssr & gatsby-browser. In gatsby node you'll have to use the
|
@wardpeet Thanks for the info, reverted my earlier changes and redid them, everything seems much easier now. From my testing this doesn't do "assetPrefix"
Thanks. |
I'll check this out in a bit.
That would be great! If you could do that. |
Any news on this @moonmeister? |
Think I was waiting on @wardpeet |
My bad, I flagged it to check this out tomorrow morning. I'm really sorry to keep you waiting |
i've added tests and fixed a small bug with start_url. It should all be operational now and working. I'll merge on monday, thanks @moonmeister for your work! 🙏 |
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.
Everything is green, let's do this!
Description
Modifies any path provided for a manifest icon to be prefixed with appropriate path or asset prefix.
Currently this affects all provided paths including those from manual, hybrid, and automatic modes. I think this makes the most sense, not sure if there will be any edge cases that need a work around.
This change could potentially create a breaking change for people using asset prefix in manual/hybrid mode who have provided full paths to work around the plugin not handling this for them,.
Documentation
I haven't written any, Do we think we should document this change in behavior?
Related Issues
Fixes: #18497