Closed emilos closed 4 years ago
@emilos I'm sorry for the trouble! I've just released a 0.55.0
. Would it solve the problem on your side?
I absolutely agree with adding specs and linter. I'll dive into this tonight. By the way, we could have a call in the afternoon if you're available.
Thanks, works now! Having some other issues, but they seem unrelated to this one, so closing.
The current version in npm seems to be broken:
The issue seems to be fixed in the meantime, do you mind publishing a new one?
It might be a good idea to add some basic local specs and set up a linter (like standard.js) to avoid issues like this.
I'd be happy to help if those ideas make sense to you.