1 | true;exports.getRawProjectId=getRawProjectId;var _child_process=require("child_process");// Q: Why does Next.js need a project ID? Why is it looking at my git remote?
;exports.__esModule= |
2 | // A:
|
3 | // Next.js' telemetry is and always will be completely anonymous. Because of
|
4 | // this, we need a way to differentiate different projects to track feature
|
5 | // usage accurately. For example, to prevent a feature from appearing to be
|
6 | // constantly `used` and then `unused` when switching between local projects.
|
7 | // To reiterate,
|
8 | // we **never** can read your actual git remote. The value is hashed one-way
|
9 | // with random salt data, making it impossible for us to reverse or try to
|
10 | // guess the remote by re-computing hashes.
|
11 | function _getProjectIdByGit(){try{const originBuffer=(0,_child_process.execSync)(`git config --local --get remote.origin.url`,{timeout:1000,stdio:`pipe`});return String(originBuffer).trim();}catch(_){return null;}}function getRawProjectId(){return _getProjectIdByGit()||process.env.REPOSITORY_URL||process.cwd();}
|
12 | //# sourceMappingURL=project-id.js.map |
\ | No newline at end of file |