yarn global add trakk-js

npm install -g trakk-js

{
    /* a valid Trakk.js API key */
    "key": "3b2b21f3-9c99-40f4-b7c4-2f358216776c",

    /* 
      * The command you use to start your app locally, 
      * from within your app's root folder
      */
    "start": "react-scripts start",

    /*
      * A list of globs to folders and/or files to trakk
      *
      * This field is optional
      *
      * By default, all .js, .jsx, .ts & .tsx files in your app 
      * will be trakked across all folders
      */
    "include": ['/my-app/**'],

    /*
      * A list of globs to folders and/or files to not trakk
      *
      * This field is optional
      *
      * By default, everything under /node_modules will be ignored, always
      */
    "exclude": ['/dist/**', '/tests/**', '/mirage/factories/**', '/path/to/my-file.js'],

    /*
      * This field is optional
      *
      * Its default value is `false`
      * 
      * Meaning that, by default, when clicking on the Trakk.js toggle button, the Trakk UI Panel
      * will slide-in providing you with a complete UI you can interact with:
      * 
      * - you can view all trakked events in real-time
      * - ignore the ones you are not interested in
      * - view all relevant stats
      * - generate documentation with a single click
      * 
      * However, for large-scale applications, if the events being trakked start to become too many (10000+) at some point, 
      * it is possible that the real-time UI Panel's responsiveness might start to slow down. 
      * 
      * The UI Panel will continue to function as expected but it might take longer for new events to be loaded and rendered in the UI.
      * 
      * If you are interested in only generating documentation automatically,
      * setting this property to true, will load the Trakk.js toggle button on your app,
      * but clicking on it will not load the Trakk.js real-time UI Panel.
      * 
      * Instead it will immediately generate documentation for you and save it locally.
      * 
      */
    "light": true,

    /*
      * This field is optional
      *
      * Its default value is `false`
      * 
      * Meaning that, by default, if your application happens to throw an Error
      * and your application is not set up to catch it, the error will be thrown and
      * your application's flow might break.
      * 
      * The uncaught Error will be trakked and reported under the "Uncaught Errors" section of the Trakk.js UI
      * 
      * If, however, you choose to set `"catchUncaughtErrors": true`,
      * then any unexpected errors thrown by your application, will, instead, be caught by Trakk.js,
      * thus preventing your application from possibly breaking its flow.
      * 
      * The Error will still be trakked and reported under the "Uncaught Errors" section of the Trakk.js UI
      * 
      * Depending on your needs, you might, or might not, desire to set `"catchUncaughtErrors": true`
      * 
      */
    "catchUncaughtErrors": true
}