Review our alternate installation methods.
  • Loader Script
    • Learn about the proview JavaScript Loader Script
  • NPM (Not yet launched)
    • Learn about installing with NPM.

​
How to Decide which installation method to use

Depending on the concrete needs of your application, you may wonder which installation method you should use.

​
Why Choose the Loader Script Over NPM

Using the Loader Script is the easiest way to start using proview. Add a script tag to your application, and we’ll take care of setting everything else up correctly for you.
  • Easy to set up: Just add a script tag to your application.
  • Easy to upgrade: We’ll take care of always shipping the latest version of the SDK to your users. No action’s needed from you. This ensures you’ll always get the latest features and bug fixes of the proview SDK.
  • Easy to add additional configuration: You can configure the SDK to your liking via window.proviewOnLoad.

​
Why Choose NPM Over the Loader Script (Yet to be launched)

While using the Loader Script has definite advantages, it also comes with some drawbacks. In these scenarios, using the npm package is the better choice:
  • Framework-specific initialization: As of now, the Loader Script only provides generic Browser JavaScript instrumentation. This means that you won’t get any React, Vue, or similar framework-specific features for proview. To get these features, you’ll need to install the framework SDK (e.g. @talview/atx-embedded-app) via npm.
  • Full control over the SDK version: If you need full control over the SDK version, you’ll need to install the SDK via npm.