Just fixed this a few minutes ago, thanks to those who told me about it! (look for v1.4.2 on npm and the corresponding commit on github)