Lightning Out 2.0 Limitations

Be aware of current Lightning Out 2.0 limitations.

  • Lightning Out 2.0 supports embedding only custom Lightning web components (LWC). To use a standard LWC component, wrap the component in a custom Lightning web component. The standard component may not be fully styled, or behave as documented, when it’s used in a Lightning Out 2.0 app.
  • Lightning 2.0 doesn’t support embedding Aura components, including any custom or standard Aura components.
  • Lightning Out 2.0 requires third-party, or cross-origin, cookies. End users must enable third-party cookies in their browser. Additionally, make sure that cross-domain Salesforce session cookies are enabled in your org. See Prepare to Build a Lightning Out 2.0 App in Salesforce Help.
  • You can’t load the Lightning Out 2.0 JavaScript library from a Lightning web component because Lightning Web Security (LWS) blocks ‌the insertion of HTML script elements. Instead, load the Lightning Out 2.0 JavaScript library directly from the host page.
  • Lightning Out 2.0 doesn’t support page navigation for embedded LWC components. The lightning/navigation service isn’t supported.
  • Lightning Out 2.0 apps are currently only available to authenticated Salesforce users. Unauthenticated user access isn’t supported yet.
  • Lightning Out 2.0 doesn’t support authorization with the OAuth 2.0 JWT bearer flow or the OAuth 2.0 client credentials flow. See Set Up Authentication for Lightning Out 2.0 in Salesforce Help.
  • To view limitations specific to passing component styles and other properties, see Set Component Styles and Properties in a Lightning Out 2.0 App.

See Also