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 🙏

© 2024 – Pkg Stats / Ryan Hefner

cordova-javascript-connector

v1.3.0

Published

Better cordova deviceready handling with waiting, callbacks, and helpers for executing cordova commands

Downloads

3

Readme

cordova-deviceready-manager

Installation

# With npm
npm i cordova-deviceready-manager


# With yarn
yarn add cordova-deviceready-manager

Usage

Initialization

You first need to initialize the package. This should happen early on as your app is initializing everything.

import {initDeviceReady} from "cordova-deviceready-manager";

initDeviceReady({
    onDeviceReady: () => /* ... Do something when its ready */
    maxWaitTime: 20 * 1000
});

You don't have to provide any options to this function at all if you don't want to:

initDeviceReady();

The "onDeviceReady" function in initDeviceReady provides an opportunity to do some additional or special setup as soon as the deviceready function fires. However, this usually isn't necessary and you can just use the onPluginReady function.

onPluginReady

onPluginReady allows you to independently bind as many function callbacks to as many plugins as you need. This allows you to safely put plugin functionality anywhere in your application without having to worry about initialization, or even if cordova is available in that context.

The following is an example of how you could use this package with cordova-plugin-statusbar.

import {onPluginReady} from "cordova-deviceready-manager";

onPluginReady("StatusBar", StatusBar => {
    // This code will not execute unless and until the plugin is available
    StatusBar.show();
});

Spelling of the first argument, the name of the plugin, is important. Make sure you match the way the plugin exports. You can name the argument in your callback function whatever you'd like though.

If you want a promise, you can use the promise form instead:

onPluginReadyPromise("StatusBar")
    .then(StatusBar => {
        StatusBar.show();
    });

You can also provide a mock version of the plugin for testing outside of the target device

onPluginReady("StatusBar", { fallback: MockStatusBar }, StatusBar => {/* ... */})

Building with Webpack

To make it easier to develop robust, clean plugins, this package comes with a CLI tool with basic Babel/webpack functionality.

npx pluginbuilder build index.js

This will produce a file called plugin.js that should be more compatible with older browsers and consolidates your plugin javascript into a single file; allowing you to divide your file up into cleaner parts and even use npm dependencies.