Split out vercel.cache and its dep vercel._internal.telemetry#160
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
I intend to use `vercel.cache` as a backend option for queue task result storage in upcoming integrations. To avoid the full SDK dependency, split `vercel.cache` into a standalone package following the footsteps of `vercel.oidc`. Aside from `vercel.headers` (already standalone), `vercel.cache` depends on the `vercel._internal.telemetry` client package, so split that out as well as `vercel.internal.telemetry`.
elprans
force-pushed
the
elprans/factor-out-vercel-cache
branch
from
e5e6d2f to
0d7d441
Compare
ricardo-agz
approved these changes
Jul 9, 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
2 participants
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.
I intend to use
vercel.cacheas a backend option for queue taskresult storage in upcoming integrations. To avoid the full SDK
dependency, split
vercel.cacheinto a standalone package following thefootsteps of
vercel.oidc. Aside fromvercel.headers(alreadystandalone),
vercel.cachedepends on thevercel._internal.telemetryclient package, so split that out as well as
vercel.internal.telemetry.