Closed dominicbarnes closed 6 years ago
I haven't tested that in a while. To be truthful, the JS code is very old and doesn't have unit tests, but I haven't had much time to replace it. I'll see if I can fix this.
I was just about to ask the same question. Any luck with a fix?
Apologies for the lack of an update. I'm going to resolve this either today or tomorrow—I've got a pretty short workday today, but I'm hoping to have it resolved anyway. I'm sure the problem isn't that hard to fix.
Strangely, it seems that the Closure Compiler is somehow mangling the input JS code in such a way that it breaks using regular numbers. I'll need to look at this more closely tonight.
Alright - could you try again with the latest build? I've updated to 1.5.1. I also updated the NPM package (forgot to do that for 1.5.0... oops.)
The problem was some variables weren't being protected from name mangling.
Working fine for me, thanks!
I'll take a look at this tonight! Thanks :)
Let me know if anything's wrong, assuming it works for now. 😊
According to the docs and #2, I should be able to do something like:
But when I try to decorate the node, I just get the following warning message:
I thought maybe this was just a problem with the npm build, but I get the same issue on the overview page. You can reproduce this with a very big hack on the console there: