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
When running my app locally, I got TrackJs working in a browserify bundled file by setting token before init and by using the global variable. (see #2)
But then when I call trackJs.track("test") it tries to post the error to localhost, resulting in an error.
My server is localhost:9000, but the served html page for my SPA has a head base url = localhost:8080. I don't know at all why TrackJs would use this url instead of an hardcoded url to your API
Actually it seems to work better since I now load my bundle with crossorigin attribute.
You may document that, and also recommend https://github.com/nodeapps/http-server as it's a simple http server in command line that support cors (useful for SPA devlopment)
When running my app locally, I got TrackJs working in a browserify bundled file by setting token before init and by using the global variable. (see #2)
But then when I call trackJs.track("test") it tries to post the error to localhost, resulting in an error.
My server is localhost:9000, but the served html page for my SPA has a head base url = localhost:8080. I don't know at all why TrackJs would use this url instead of an hardcoded url to your API
POST -> http://localhost:8080/?token=mytoken
The text was updated successfully, but these errors were encountered: