OK, I'm a dumbass. I skimmed the issue and thought it was a duplicate of another I was having trouble tracking down. No, this is me duplicating the extension. Didn't notice because it wasn't erroring out for me, for some reason.
Should be fixed in 1.0.2. Do let me know if it works now, since I can't test it locally.