Interestingly, it's not a simple drop-in replacement when issuing Google fonts in a NEXT.js app's `_document.js` head. I have a CORS error, though Google fonts worked previously without any additional config. Does NEXT.js whitelist Google fonts in their routing? Or would there be a difference in how the "bunny" drop-in behaves with CORS headers?