This is the .ember-cli file.
{
/**
Ember CLI sends analytics information by default. The data is completely
anonymous, but there are times when you might want to disable this behavior.
Setting `disableAnalytics` to true will prevent any data from being sent.
*/
"disableAnalytics": false
}
Who does Ember CLI send analytics to by default?
Isn't it amazing that we can track anything in our tools when it has open sources? Let's track together.
The question: what is it in general?
The answer: the analytic tool is leek, which is made for GA tracking. Obviously it requires a tracking code, so we can see where it is populated. The very code is here.
The question: what it tracks?
The answer: I don't know every tracking library, but we can find something useful in a repo. There are 3 tracking commands - trackEvent
, trackError
, and track
. Later I found one more - trackTiming
.
Let's use native Github search in order to know, how it is used in ember-cli project. Nothing for .trackEvent
; the only positive relevant for .trackError
- sending an error message. But a general .track
is used more frequent - I had to use a limiting parameter in the search. So the final list of events - addition/changing of file, building/rebuilding time, live reloading event, and something not obvious here.
The question: I just asked who is a recipient, why can't you answer directly?
The answer: now we know, that the main player here is leek, so let's go through it. The library is very small, hence we could even bruteforce it. The main file has the only important method, where we can easily see the source of url. The module is in the same folder, and unfortunately our journey ends here.