From be082509028677bc8a3afb254acab2e1d2e304a2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivar=20Conradi=20=C3=98sthus?= Date: Thu, 9 Sep 2021 10:39:34 +0200 Subject: [PATCH] docs: add react-sdk to proxy docs. --- websitev2/docs/sdks/unleash-proxy.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/websitev2/docs/sdks/unleash-proxy.md b/websitev2/docs/sdks/unleash-proxy.md index cf2d6626dd..059a84e971 100644 --- a/websitev2/docs/sdks/unleash-proxy.md +++ b/websitev2/docs/sdks/unleash-proxy.md @@ -122,9 +122,8 @@ The Unleash Proxy takes the heavy lifting of evaluating toggles and only returns However in some settings you would like a bit more logic around it to make it as fast as possible, and keep up to date with changes. - [JavaScript Proxy SDK](/sdks/proxy-javascript) +- - [Ract Proxy SDK](/sdks/proxy-react) - [Android Proxy SDK](/sdks/android_proxy_sdk) - [iOS Proxy SDK](/sdks/proxy-ios) -- React SDK (coming soon) -- React Native SDK (coming soon) The proxy is also ideal fit for serverless functions such as AWS Lambda. In that scenario the proxy can run on a small container near the serverless function, preferably in the same VPC, giving the lambda extremely fast access to feature flags, at a predictable cost.