See this issue on GitHub for more info.
A fix for the above issue was merged quite a while ago, but a new version hasn’t been published to npm. I’m not sure if this is the best place to mention this, but I was hoping to get someone’s attention and get it published 
Hey @rjmccluskey!
It’s a good place to mention that Sorry for the inconvenience. Already communicated your feedback to our product team so they can publish it soon to npm. Thanks a lot!
For future reference, the fastest way to get such thing let’s say implemented is to hit our product team directly via our feedback site:
This ways it’s added to our product backlog and then accordingly prioritized. Watch out for the update