You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visiting my website with goatcounter gives this error:
I only looked through the code very cursorily but 85f3c30 looks suspicious — count now takes one argument count_vars instead of none, but the invocation of count() on load at the bottom passes in zero arguments.
The text was updated successfully, but these errors were encountered:
Thanks, I fixed it when I woke up this morning: db1a509. What a silly error; sorry :-( I had tested it on my own site before deploy using the proxy script, but I forgot that I include the script in the page directly (it's a bit faster that way), so the new version never got loaded 🤦
I spent quite some time trying to add decent tests to the JavaScript code a few months ago, but wasn't really able to find a good solution. There are many JS testing frameworks, but I'm not a huge fan of these kind of large framework and would prefer a simple "test runner". I spent some time trying to get my own solution working, but the whole browser context thing makes stuff kinda tricky and had loads of other things to do as well :-/
Visiting my website with goatcounter gives this error:
![2019-12-06-183356_1920x1080_scrot](https://user-images.githubusercontent.com/3482833/70363630-28907a80-1857-11ea-8a14-369a655b9c25.png)
I only looked through the code very cursorily but 85f3c30 looks suspicious —
count
now takes one argumentcount_vars
instead of none, but the invocation ofcount()
on load at the bottom passes in zero arguments.The text was updated successfully, but these errors were encountered: