Stack Overflow
Stack Overflow

Questions tagged [trackjs]

trackjs.com is online service for monitoring your client side applications.

Trackjs.com allows you to see basically every error that would otherwise stay forgotten in user's console.

The Web is the most hostile development environment imaginable. When the frontend inevitably breaks for your visitors, TrackJS helps find and fix your JavaScript errors fast, so you can get back to work.

10 questions
2
votes
2 answers

TrackJS and GDPR and SPA

I'm using TrackJS in SPA, i have logic related to GDPR, so I can NOT send any data before consent given. I found onError config option which help with this. But i still have external request to https://usage.trackjs.com/usage.gif. I can disable this…
Alexandr Vysotsky
  • 1,081
  • 13
  • 16
2
votes
1 answer

How to ignore TrackJS errors originating from scripts linked from other domains?

TrackJS detects errors occurred in all JavaScript code on the page — be it inline code, scripts linked from the same domain or other domain names. Most of the JS code linked from other domain names (such as various marketing tags, trackers etc.) is…
Greendrake
  • 3,657
  • 2
  • 18
  • 24
2
votes
1 answer

trackJS XML Parsing Error: no element found in firefox

I have implemented trackJS library for better debugging and logging. But whenever I send any error to trackJS it throws error only in Firefox. XML Parsing Error: no element found Location: https://capture.trackjs.com/capture?token= Line…
pratik nagariya
  • 574
  • 5
  • 21
1
vote
1 answer

Trackjs: ignore rules by token in user agent

In TrackJS, some user agents are parsed as normal browsers, e.g.: Mozilla/5.0 (Linux; Android 7.0; SM-G930V Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.125 Mobile Safari/537.36 (compatible; Google-Read-Aloud;…
Alexandr Vysotsky
  • 1,081
  • 13
  • 16
1
vote
1 answer

TrackJS: how to prevent attackers from using my token?

I'm planning to use TrackJS to monitor errors from my app but by reading the documentation it seems that my private token must be exposed on the browser: