I have seen this same error locally, and I thought it was a regression but while I was trying to determine when this would have regressed (via git bisect) it magically got solved. I believe it was because there was a corrupt build cache that got reset while bisecting.
In a production environment, you can try rebuilding your site, there is a good chance that it will resolve the issue.