npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@saritasa/pager-in-app-browser

v7.0.2

Published

Capacitor In-App Browser plugin for the Pager project

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

golovachev-saritasagolovachev-saritasaandrey-saritasaandrey-saritasamaximkorkin-saritasamaximkorkin-saritasasaritasa-npmsaritasa-npmko-vasilev-saritasako-vasilev-saritasadbitkovski-saritasadbitkovski-saritasa

Keywords

capacitorpluginbrowsernative

Readme

@saritasa/pager-in-app-browser

Capacitor In-App Browser plugin for the Pager project.

Install

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

Usage

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

InAppBrowser.open("YOUR_URL");

Actually, this plugin is fork of @capgo/inappbrowser plugin. Read about available methods and API there.

Update

It is recommended to update the plugin after updating the @capgo/inappbrowser plugin to successfully handle breaking changes.

Anyway, you can try updating without waiting for the @capgo/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. 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 project and check all cases from the support section.

Support

The main purpose of the plugin is to change or add the behavior of @capgo/inappbrowser, for the purposes and goals of the Pager 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).