Disable Yarn telemetry by default in jlpm#118
Merged
Conversation
krassowski
approved these changes
Jun 20, 2026
krassowski
left a comment
Member
There was a problem hiding this comment.
Makes sense to me, thank you!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #114
Description
Yarn Berry ships with
enableTelemetry: true, so jlpm has been quietly sending anonymous usage data to Yarn's servers. JupyterLab users install via pip/conda and never opt into Yarn directly, so they likely have no idea this is happening and there's a known bug where the telemetry ping can hang the CLI for several minutes on locked-down networks. (yarnpkg/berry#6271)This sets
YARN_ENABLE_TELEMETRY=0as a default in the jlpm launcher, before we execnode + yarn.js.Uses
os.environ.setdefault, so it's a soft default and anyone who wants telemetry back can exportYARN_ENABLE_TELEMETRY=1.