-
Notifications
You must be signed in to change notification settings - Fork 394
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 Heroku Caching #2898
Fix Heroku Caching #2898
Conversation
ece8a7f
to
d3075e7
Compare
a2c9a78
to
d3075e7
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.
Looks great! The only issue I noticed was that the Community/styles.module.css
doesn't seem to be converted to regular css correctly:
It looks fine on my iphone safari, but my Windows Brave Browser and Firefox browser show the bug. I wasn't able to test on my Mac since I don't have it with me at the moment.
I think you meant to reply on #2851, I got a little confused when I didn't see the issue here but found it when I checked there. Great catch! I'll get on that. |
Yep 😅 |
Closing in favor of #2851 |
This backports the script from #2851 that fixes Heroku caching by keeping the build path stable. It doesn't include any upgrades to Gatsby and its plugins, since there seems to be a lot of weirdness with
sharp
version mismatches.Even with nothing else, this should speed up caching (after the first run) with very little drawbacks. #2851 is coming as well, but it'll need some babysitting as some existing Gatsby 2 apps break and need their cache turned off to re-add the new one.
It also adds a
retry
option toDEPLOY_OPTIONS
that allows us to disable the "clear-and-retry" attempt which helps with debugging cache issues rapidly.