Migration from V2 to V3

overview this guide explains how to migrate from intelliwidgets v2 (javascript sdk) to intelliwidgets v3, which is based on web components intelliwidgets v3 introduces a simpler and more modern integration approach, reducing the amount of setup and javascript required to render widgets on your platform core concept the main change in v3 is how widgets are integrated v2 (sdk) uses a javascript api to create and mount widgets imperatively v3 (web components) uses native html elements to render widgets declaratively in practice, this means you no longer need to initialize an sdk instance you no longer mount widgets using selectors widgets are placed directly in your html a shared \<ip session> component replaces the sdk instance and provides global configuration (such as authentication and language) this shift makes integrations easier to maintain and avoids common issues such as css or script conflicts across different frameworks step by step migration replace the sdk script remove the v2 sdk script \<script src="https //cdn intelliprove com/packages/intelli widgets/v2/latest js">\</script> add the v3 script remove sdk initalization in v2, you initialize the sdk const intelli = intelliprovewidgets("\<user action token>"); in v3, this is replaced by the \<ip session> component the session component provides global configuration such as authentication and language replace mountwidget with components in v2 intelli mountwidget("#biomarker", "biomarker", { face scan id " ", parameter "respiratory rate" }); in v3 widgets are now rendered declaratively using html wrap all widgets in session all intelliprove web components must be placed within an \<ip session> this replaces the sdk instance and ensures all widgets share the same configuration language handling in v2 intelli changelanguage("en"); in v3 theming v3 widgets are built as web components, making them more flexible and customizable than in v2 customization options are continuously being expanded if your v2 integration uses custom styling, you may need to adjust how these are applied in v3 for more information, refer to the docid\ wwt6qejyzjvb5jnvzgmjc page