open-index/open-npm huggingface dataset:
npm package: @saritasa/pager-in-app-browser
Description: Capacitor In-App Browser plugin for the Pager project
Author: Saritasa
Latest version: 7.0.2

# @saritasa/pager-in-app-browser

Capacitor In-App Browser plugin for the [Pager](https://github.com/saritasa-nest/pager-frontend) project.

## Install

```bash
npm install @saritasa/pager-in-app-browser
npx cap sync
```

## Usage

```js
import { InAppBrowser } from '@saritasa/pager-in-app-browser'

InAppBrowser.open("YOUR_URL");
```

Actually, this plugin is fork of [@capgo/inappbrowser](https://github.com/Cap-go/capacitor-inappbrowser) plugin. Read about available methods and API there.


## Update

It is recommended to update the plugin after updating the [@capgo/inappbrowser](https://github.com/Cap-go/capacitor-inappbrowser) plugin to successfully handle breaking changes.

Anyway, you can try updating without waiting for the [@capgo/inappbrowser](https://github.com/Cap-go/capacitor-inappbrowser) plugin to be updated, just make sure that everything is being built and working.

1. Update capacitor to latest version following all the points from the [official guide](https://capacitorjs.com/docs/updating/7-0). Don't forget to select actual version.
2. Update additional deps if need.
3. Bump version of the project to be able to publish the package. **Please** bump the version so that **the major version matches the capacitor version**.
4. Build and verify that all works fine.
5. After updating, it is recommended to install the new plugin to [Pager](https://github.com/saritasa-nest/pager-frontend) project and check all cases from the [support](#support) section.

## Support

The main purpose of the plugin is to change or add the behavior of [@capgo/inappbrowser](https://github.com/Cap-go/capacitor-inappbrowser), for the purposes and goals of the [Pager](https://github.com/saritasa-nest/pager-frontend) project.

Cases for which we use our solution and which need to be tested after each update:

1. The basic plugin incorrectly processed a click on the URL, which led to a redirect. Because of this, the logout button did not work correctly.
   > **How to check that everything is OK** - click the logout button and see that the application returned to the login page.
2. The basic plugin did not handle the hardware back button correctly on Android devices.
   > **How to check that everything is OK** - press the hardware back button on the device until a modal appears, confirming which should close the application.
3. The basic plugin incorrectly opened a webview page if an HTML string was passed to it instead of a URL.
   > **How to check that everything is OK** - open the app in iOS device and check that after login pager app has been loaded in webview.
4. The basic plugin incorrectly processed URLs leading to opening the system UI, for example `tel:`.
   > **How to check that everything is OK** - open the app, log in, open a similar link, the application should call a system UI (for example, go to writing a message or contact book).