-
Notifications
You must be signed in to change notification settings - Fork 12
Use ANDROID_SDKLESS client with TV fallback #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
alexeichhorn
merged 1 commit into
cloudflare-worker
from
feature/android-sdkless-client
Jan 19, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
youtubei.js repository alexeichhorn YouTube.js feat/android-sdkless-client branch💡 Result:
I couldn't find a GitHub repository or branch matching "alexeichhorn / youtubei.js" or a branch named "feat/android-sdkless-client". I found alexeichhorn’s YouTubeKit repo (Swift) and the main YouTube.js (youtubei.js) project (LuanRT), but no fork or branch by that name. Sources: GitHub listing for alexeichhorn/YouTubeKit [1] and the YouTube.js (youtubei.js) repo (LuanRT) [2].
If you have a direct GitHub URL or more details (exact username spelling or repo owner), share it and I’ll look again.
Sources:
[1] https://github.com/alexeichhorn/YouTubeKit
[2] https://github.com/LuanRT/YouTube.js
🌐 Web query:
youtubei.js ANDROID_SDKLESS client releases tags commits💡 Result:
Here are the places that match your query and where you can find releases/tags/commits related to the Android (sdkless) client for youtubei.js / InnerTube tooling:
Sources:
[1] GitHub — LuanRT/YouTube.js Releases & Tags.
[2] YouTube.js API / Constants — CLIENTS (ANDROID) (ytjs.dev).
[3] yt-dlp commit showing android_sdkless client context.
🌐 Web query:
site:github.com alexeichhorn YouTube.js releases tags💡 Result:
I couldn't find any GitHub releases/tags for a repository named "YouTube.js" under the user alexeichhorn. The YouTube.js project with releases is LuanRT/YouTube.js (releases page). [1]
For reference, alexeichhorn's GitHub contains YouTubeKit and other repos (not YouTube.js). [2]
Sources:
🏁 Script executed:
Repository: alexeichhorn/YouTubeKit-Server
Length of output: 581
🌐 Web query:
github.com/alexeichhorn/YouTube.js android sdkless💡 Result:
Short answer: alexeichhorn does not have a repo named YouTube.js on GitHub. The YouTube.js (youtubei.js) project you probably mean is LuanRT/YouTube.js, and Alex Eichhorn maintains YouTubeKit (an iOS extractor), not an Android "sdkless" YouTube.js. [1][2]
Options if you want an Android, SDK-less approach:
Sources:
🌐 Web query:
"alexeichhorn/YouTube.js" fork💡 Result:
Do you mean a fork of the GitHub repo "alexeichhorn/YouTube.js"? If so, do you want me to (pick one)
Tell me which and I’ll search GitHub and return results with links.
Verify the GitHub fork and pin to a commit or tag.
The repository
alexeichhorn/YouTube.jsdoes not appear to exist publicly on GitHub. The official YouTube.js project is maintained at LuanRT/YouTube.js. Confirm whether this is a private fork, an incorrect reference, or if the dependency should point to a different source. Once verified, pin the dependency to a specific commit SHA or tag rather than a branch ref to ensure reproducible builds and reduce supply-chain risk.🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is my own github fork
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alexeichhorn, thank you for clarifying! Since this is your own fork, the dependency reference is perfectly valid. I apologize for the confusion—my initial concern was based on not finding the fork in public indexes.Using a branch reference makes sense for active development. If you plan to merge this to production later, you might consider pinning to a specific commit SHA for reproducibility, but that's entirely up to your workflow preferences.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The lockfile does that, doesn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alexeichhorn, you're absolutely right! The lockfile does indeed pin the dependency to a specific commit SHA. When your package manager (npm, yarn, or pnpm) resolves the GitHub branch reference during installation, it records the exact commit SHA in the lockfile. This ensures reproducible builds across environments as long as the lockfile is committed to the repository.My concern about reproducibility is fully addressed by this mechanism. Sorry for the noise on this one!