This appears to be a repeat of #212 and #226, the issue was previously resolved but seems to have resurfaced. After some digging, it looks like that the regression was introduced in v1.0.0-beta.11, more specifically #282.