You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs for configuring with Vercel's Edge runtime say to use PluggableStorage and ErrorLogger, but neither is exported from @splitsoftware/splitio.
Why I Care / Use-Case
I have a Vercel application that includes some code that runs on the Edge runtime and some in the Serverless (Node) runtime. I use feature flags in both runtimes. I want the logic for handling feature flags to be consistent across the two runtimes and I don't want to maintain two implementations / integrations with Split.
Both packages declare the same SplitIO Typescript namespace, which results in collisions like this one:
Background
The public API for javascript-client has diverged from the one for javascript-browser-client. For example,
Specifically, the @splitsoftware/splitio API will look like the @splitsoftware/splitio-browserjs one, to support PluggableStorage (i.e., custom storages) for both client-side (client.getTreatment(FEATURE_FLAG_NAME)) and server-side (client.getTreatment(USER_ID, FEATURE_FLAG_NAME)) API styles.
But unfortunately, at the moment, you cannot use PluggableStorage with the @splitsoftware/splitio package, so it is not compatible with the Vercel Edge integration because this requires the EdgeConfigWrapper to connect the SDK to the Edge Config instance.
Question / Problem
Is the Vercel edge integration compatible with the isomorphic JavaScript library?
The docs for configuring with Vercel's Edge runtime say to use
PluggableStorage
andErrorLogger
, but neither is exported from@splitsoftware/splitio
.Why I Care / Use-Case
I have a Vercel application that includes some code that runs on the Edge runtime and some in the Serverless (Node) runtime. I use feature flags in both runtimes. I want the logic for handling feature flags to be consistent across the two runtimes and I don't want to maintain two implementations / integrations with Split.
Both packages declare the same
SplitIO
Typescript namespace, which results in collisions like this one:Background
The public API for
javascript-client
has diverged from the one forjavascript-browser-client
. For example,versus
See also splitio/javascript-client#781
The text was updated successfully, but these errors were encountered: