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

@havesource/create-cordova-plugin

v1.0.1

Published

Quickly create Cordova plugin starter structure.

Downloads

5

Readme

@havesource/create-cordova-plugin

A scaffolding tool for generating a basic structure for a Cordova plugin.

How to Use

Without Installing Globally or to a Project-Scope

% npm init @havesource/cordova-plugin

Using a Global Installation

% npm install -g @havesource/cordova-plugin
% create-cordova-plugin

Using a Project-Scope Installation

% npm install @havesource/cordova-plugin
% npx create-cordova-plugin

About the CLI Input Prompts

  1. ID (npm package & directory name): (cordova-plugin-sample)

    This is the directory and plugin name.

    The following area will be set:

    • package.json for the name and cordova.id fields.
    • plugin.xml for the id attribute.
  2. Readable Name: (Cordova Sample Plugin)

    This is a human-readable name for the plugin, which is set in the name element of the plugin.xml file.

  3. Description: (A sample Cordova plugin.)

    A brief description of your plugin, which will be added to the description field in the npm package.json and plugin.xml files.

  4. License (SPDX format)

    Specify the license your plugin will use, following the SPDX format.

    It will be added to the license field in the npm package.json and plugin.xml files.

    If you have a custom or proprietary license, enter "SEE LICENSE IN LICENSE", and be sure to create a LICENSE file.

  5. Author

    This is optional.

    If provided, it will be added to the author field in the npm package.json and plugin.xml files.

    When empty, the author field will still be created but with empty values.

  6. Supported Platform: (Press to select, to toggle all, to invert selection, and to proceed)

    Select the platforms that your plugin will support.

    The tool will populate the platforms section in the package.json, the corresponding platform elements in the plugin.xml, and create mocked native folders and files.

  7. API Name: (SamplePlugin)

    This will be the name used when creating the native class files of the supported platform you pick and the front-end JS API of your plugin.

  8. Android Package Name: (com.example.sampleplugin)

    This prompt appears if you selected Android as a supported platform. Enter the package name that will be used for the Android plugin code. This should be distinct from your app’s package name.