fix: add SOCKS proxy example and fixes warning logging and proxyAuth reporting#1786
Merged
Conversation
The SDK cannot inspect a caller-supplied proxyAgent to know whether it carries its own credentials (for example a SOCKS URL's embedded username/password), so usingProxyAuth() now reports true for any supplied proxyAgent rather than only when proxyOptions.auth is set, matching the existing best-effort reasoning for usingProxy().
Contributor
|
@launchdarkly/js-sdk-common size report |
Contributor
|
@launchdarkly/browser size report |
Contributor
|
@launchdarkly/js-client-sdk-common size report |
Contributor
|
@launchdarkly/js-client-sdk size report |
joker23
force-pushed
the
skz/sdk-2508/socks-proxy-example
branch
from
July 1, 2026 18:31
1933703 to
30421d6
Compare
kinyoklion
reviewed
Jul 1, 2026
kinyoklion
approved these changes
Jul 6, 2026
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.
This PR mainly adds an example for how to use SOCKS proxy agent in node server sdk
Additionally this PR will pull in fixes that were not included in the previous PR
proxyAgentoption will no longer log a "unknown property" warningproxyAgentwill also reportproxyAuthusage to diagnostic eventNote
Low Risk
Changes are limited to Node-specific networking/diagnostics behavior, documentation, and CI; no auth or data-path redesign beyond more accurate diagnostic flags when using custom agents.
Overview
Adds a custom SOCKS proxy example for the Node server SDK that wires
SocksProxyAgentintoproxyAgent, plus Dante-based proxy assets and a CI job that runs the example and checks proxy logs for real traffic.Fixes
proxyAgenthandling: strip it from options passed into sharedLDClientImplso it is not logged as an unknown config option, and treat a suppliedproxyAgentas a best-effort signal for proxy auth in diagnostics (usingProxyAuth()/_hasProxyAuth), matching SOCKS URLs with embedded credentials. Tests andLDOptionsdocs are updated accordingly; the example is registered in workspaces, release-please, and excluded from the main SDKtsconfigbuild.Reviewed by Cursor Bugbot for commit 55e41b9. Bugbot is set up for automated code reviews on this repo. Configure here.