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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@juit/capacitor-updater

v0.1.39

Published

Capacitor utility to update an app from a ZIP file

Readme

Juit Capacitor Updater

This library demonstrates how to perform Capacitor live updates, which update the contents of the web application without requiring an update from the app store.

Please note that this is not intended to be production quality, but rather a simple showcase of the interaction between different Capacitor APIs that can be used to perform live updates.

Outline

When Capacitor starts, it serves the web application bundled within the binary itself (the .ipa for iOS or .apk for Android).

The updateCapacitor(...) function performs the following steps:

  1. Downloads a ZIP file from the specified URL.
  2. Uses JSZip to extract the downloaded ZIP file in the Library directory of the app, following Capacitor's updates naming scheme.
  3. Provides a callback to reload the current web view, pointing the root to the extracted ZIP file.

Upon restart, the persistUpdates() function can be called to persist the server base path (where the ZIP file was extracted) and use this for all subsequent uses of the app (e.g., when forcefully restarted).

Functions

This library exposes two functions:

updateCapacitor(...)

The updateCapacitor(...) async function downloads the specified URL, extracts it on the local device, and provides a callback to reload the web view with the updated content. It accepts the following arguments:

  • url (required): A string or URL from which the ZIP file will be downloaded.
  • progress (optional): A callback that will be invoked with a number between 0 and 1 indicating progress. Between 0.5, the progress indicates download; between 0.5 and 1, it indicates unzipping progress.
  • verbose (optional): When true, the update process will be logged using console.log(...).

When successful, this function will asynchronously return a callback () => Promise<void> that needs to be invoked to reload the web view with the updated contents.

If the update could not be performed (either due to live-reload in Capacitor or when on the web) or in case of errors during downloading or unzipping, this function will throw an error asynchronously (returning a rejected promise).

persistUpdates()

Upon initialization of your app, always call persistUpdates() to ensure that app reloads will point to the latest updated code.

This function is safe to call anytime and on any platform, as it will only persist the path when the current server base path is indeed a directory created during an update with updateCapacitor(...).

This function is also asynchronous and will return a promise to a boolean indicating true when the path has been persisted.