Skip to content

change yarn telemetry to opt-in - #823

Merged
eternal-flame-AD merged 1 commit into
masterfrom
upgrade-ui-new-pm-telemetry
Aug 8, 2025
Merged

change yarn telemetry to opt-in#823
eternal-flame-AD merged 1 commit into
masterfrom
upgrade-ui-new-pm-telemetry

Conversation

@eternal-flame-AD

Copy link
Copy Markdown
Member

Since we upgraded UI I think we should disable the telemetries newer yarn versions have by default. This sets a default disable for package manager repositories for all builders, users can still opt-in with --enableTelemetry.

The legal reasoning is since we hide yarn behind make I don't really think telling the user to run make build-js counts as providing giving users an opportunity to consent.

The technical reasoning is they claim the reason as:

"Various threads in the Node docker image repositories suggested to remove Yarn from the Docker image ... because of the lack of telemetry, some projects also had trouble taking us seriously." documentation

Where? I gave it a quick check and I do not see such debates (at least the problem is not simply "I don't think it is popular enough"). Most are functional, cost, SBOM and security concerns. I don't really believe the appropriate way to be "taken seriously" out of these issues is numerically monetizing your users for your project continuity without an explicit consent.

I also don't see similar telemetry systems being coded into the NPM or PNPM command line. Go also has telemetry but they are opt-in and thus we are not making a choice on behalf of users. Yarn's opt-out approach feels particularly aggressive to me.

Their RFC: yarnpkg/berry#1250

@eternal-flame-AD
eternal-flame-AD requested a review from a team as a code owner August 8, 2025 01:09
@jmattheis
jmattheis changed the base branch from upgrade-ui to master August 8, 2025 09:01

@jmattheis jmattheis left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I didn't knew yarn had this feature.

Signed-off-by: eternal-flame-AD <yume@yumechi.jp>
@eternal-flame-AD
eternal-flame-AD force-pushed the upgrade-ui-new-pm-telemetry branch from 16dc4be to 400cf8b Compare August 8, 2025 11:26
@codecov

codecov Bot commented Aug 8, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.54%. Comparing base (ebf6a64) to head (400cf8b).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #823   +/-   ##
=======================================
  Coverage   79.54%   79.54%           
=======================================
  Files          56       56           
  Lines        2645     2645           
=======================================
  Hits         2104     2104           
  Misses        450      450           
  Partials       91       91           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@eternal-flame-AD
eternal-flame-AD merged commit ea1cc38 into master Aug 8, 2025
4 checks passed
@jmattheis
jmattheis deleted the upgrade-ui-new-pm-telemetry branch August 9, 2025 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants