quran/node_modules/next/dist/telemetry/project-id.js

"use strict";
Object.defineProperty(exports, "__esModule", {
    value: true
});
exports.getRawProjectId = getRawProjectId;
var _childProcess = require("child_process");
// Q: Why does Next.js need a project ID? Why is it looking at my git remote?
// A:
// Next.js' telemetry is and always will be completely anonymous. Because of
// this, we need a way to differentiate different projects to track feature
// usage accurately. For example, to prevent a feature from appearing to be
// constantly `used` and then `unused` when switching between local projects.
// To reiterate,
// we **never** can read your actual git remote. The value is hashed one-way
// with random salt data, making it impossible for us to reverse or try to
// guess the remote by re-computing hashes.
function _getProjectIdByGit() {
    try {
        const originBuffer = (0, _childProcess).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();
}

//# sourceMappingURL=project-id.js.map