# Embedding large third-party React SDKs

**URL:** <https://community.palantir.com/t/embedding-large-third-party-react-sdks/6651>\
**Category:** Ask the Community\
**Tags:** osdk-react\
**Created:** [May 26, 2026, 8:16am UTC](https://community.palantir.com/t/embedding-large-third-party-react-sdks/6651 "2026-05-26T08:16:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Olga](https://avatars.discourse-cdn.com/v4/letter/o/57b2e6/32.png) [@Olga](https://community.palantir.com/u/Olga)\
**Post date:** [May 26, 2026, 8:16am UTC](https://community.palantir.com/t/embedding-large-third-party-react-sdks/6651/1 "2026-05-26T08:16:22Z")

</div>

I’m building a Foundry React app with Ontology SDK integration and trying to connect Box.com as a governed content layer for Foundry records.

I successfully:

- create Box folders automatically from Foundry

- store Box folder IDs/URLs on objects

My issue is the UI layer.

I tried embedding Box Content Explorer / Box UI Elements in both:

- custom widgets

- hosted React apps

but ran into CSP restrictions and major dependency/runtime issues with Box UI Elements in Foundry’s Vite/esbuild environment.

Question:  
What is the recommended Foundry-native pattern for integrating external content systems like Box or SharePoint into React applications?

Should the UI generally be:

- native Foundry React components + external APIs instead of embedding third-party UI SDKs?

Has anyone successfully embedded large third-party React SDKs in hosted Foundry apps?