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

@interopio/cli

v4.5.0

Published

Interop.io CLI - a command line for creating Interop.io applications

Vulnerabilities

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

Links

Maintainers

smateevsmateevtsachevtsachevthorsentthorsenthristo-kolev-interopiohristo-kolev-interopioppetkowppetkowgdavidkovgdavidkovflashd2nflashd2nstaaflstaaflandy.gardnerandy.gardnerkiril.popovkiril.popovmitk0936mitk0936istoykovistoykovtrendo7trendo7

Keywords

glueglue42desktopinteropcontextserverlayoutsmetricsio.connectinterop.ioio.connect browserio.connect desktopio.connect browser platformcliio.connect cli

Readme

IO.Connect CLI

IO.Connect CLI - a command line for creating IO.Connect applications

Usage

$ npm install -g @interopio/cli
$ iop COMMAND
running command...
$ iop (--version)
@interopio/cli/4.5.0 win32-x64 node-v22.22.2
$ iop --help [COMMAND]
USAGE
  $ iop COMMAND
...
$ npm install -g @interopio/cli
$ iop COMMAND
running command...
$ iop (--version)
@interopio/cli/4.5.0 darwin-x64 node-v20.19.6
$ iop --help [COMMAND]
USAGE
  $ iop COMMAND
...

Commands

iop configure

Configure your io.Connect CLI with correct credentials.

USAGE
  $ iop configure

FLAGS
  -m, --mode=<option>  The mode to use for fetching the templates - either from a remote git repository or from an
                       embedded collection.
                       <options: auto|remote|offline>
  -t, --token=<value>  Your io.Connect Browser license key.

DESCRIPTION
  Configure your io.Connect CLI with correct credentials.

EXAMPLES
  Starts an interactive flow to configure your io.Connect CLI.

    $ iop configure

  Configures your io.Connect CLI with the provided license token.

    $ iop configure --token <license-token>

  Configures your io.Connect CLI mode to use when fetching app templates.

    $ iop configure --mode <auto-or-remote-or-offline>

  Shows help for the configure command.

    $ iop configure --help

iop help [COMMAND]

Display help for iop.

USAGE
  $ iop help [COMMAND...] [-n]

ARGUMENTS
  [COMMAND...]  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for iop.

See code: @oclif/plugin-help

iop new <NEWAPP>

Bootstraps a new io.Connect app.

USAGE
  $ iop new <NEWAPP>

ARGUMENTS
  NEWAPP  The type of new app to create: browser-platform | browser-client

FLAGS
  -n, --name=<value>       The name of your IO.Connect Browser app.
  -t, --template=<option>  The IO.Connect Browser app template.
                           <options: dev-react-seed|home-react-wsp|ng|vanilla-js|wsp-frame|ng|react|vanilla-js>
  -y, --yes                Skip prompts and use default values for all options

DESCRIPTION
  Bootstraps a new io.Connect app.

EXAMPLES
  $ iop new browser-platform

  $ iop new [email protected]

  $ iop new browser-client

  $ iop new [email protected]

iop plugins

List installed plugins.

USAGE
  $ iop plugins [--json] [--core]

FLAGS
  --core  Show core plugins.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List installed plugins.

EXAMPLES
  $ iop plugins

See code: @oclif/plugin-plugins

iop plugins add PLUGIN

Installs a plugin into iop.

USAGE
  $ iop plugins add PLUGIN... [--json] [-f] [-h] [-s | -v]

ARGUMENTS
  PLUGIN...  Plugin to install.

FLAGS
  -f, --force    Force npm to fetch remote resources even if a local copy exists on disk.
  -h, --help     Show CLI help.
  -s, --silent   Silences npm output.
  -v, --verbose  Show verbose npm output.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Installs a plugin into iop.

  Uses npm to install plugins.

  Installation of a user-installed plugin will override a core plugin.

  Use the IOP_NPM_LOG_LEVEL environment variable to set the npm loglevel.
  Use the IOP_NPM_REGISTRY environment variable to set the npm registry.

ALIASES
  $ iop plugins add

EXAMPLES
  Install a plugin from npm registry.

    $ iop plugins add myplugin

  Install a plugin from a github url.

    $ iop plugins add https://github.com/someuser/someplugin

  Install a plugin from a github slug.

    $ iop plugins add someuser/someplugin

iop plugins:inspect PLUGIN...

Displays installation properties of a plugin.

USAGE
  $ iop plugins inspect PLUGIN...

ARGUMENTS
  PLUGIN...  [default: .] Plugin to inspect.

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Displays installation properties of a plugin.

EXAMPLES
  $ iop plugins inspect myplugin

See code: @oclif/plugin-plugins

iop plugins install PLUGIN

Installs a plugin into iop.

USAGE
  $ iop plugins install PLUGIN... [--json] [-f] [-h] [-s | -v]

ARGUMENTS
  PLUGIN...  Plugin to install.

FLAGS
  -f, --force    Force npm to fetch remote resources even if a local copy exists on disk.
  -h, --help     Show CLI help.
  -s, --silent   Silences npm output.
  -v, --verbose  Show verbose npm output.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Installs a plugin into iop.

  Uses npm to install plugins.

  Installation of a user-installed plugin will override a core plugin.

  Use the IOP_NPM_LOG_LEVEL environment variable to set the npm loglevel.
  Use the IOP_NPM_REGISTRY environment variable to set the npm registry.

ALIASES
  $ iop plugins add

EXAMPLES
  Install a plugin from npm registry.

    $ iop plugins install myplugin

  Install a plugin from a github url.

    $ iop plugins install https://github.com/someuser/someplugin

  Install a plugin from a github slug.

    $ iop plugins install someuser/someplugin

See code: @oclif/plugin-plugins

iop plugins link PATH

Links a plugin into the CLI for development.

USAGE
  $ iop plugins link PATH [-h] [--install] [-v]

ARGUMENTS
  PATH  [default: .] path to plugin

FLAGS
  -h, --help          Show CLI help.
  -v, --verbose
      --[no-]install  Install dependencies after linking the plugin.

DESCRIPTION
  Links a plugin into the CLI for development.

  Installation of a linked plugin will override a user-installed or core plugin.

  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
  command will override the user-installed or core plugin implementation. This is useful for development work.


EXAMPLES
  $ iop plugins link myplugin

See code: @oclif/plugin-plugins

iop plugins remove [PLUGIN]

Removes a plugin from the CLI.

USAGE
  $ iop plugins remove [PLUGIN...] [-h] [-v]

ARGUMENTS
  [PLUGIN...]  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ iop plugins unlink
  $ iop plugins remove

EXAMPLES
  $ iop plugins remove myplugin

iop plugins reset

Remove all user-installed and linked plugins.

USAGE
  $ iop plugins reset [--hard] [--reinstall]

FLAGS
  --hard       Delete node_modules and package manager related files in addition to uninstalling plugins.
  --reinstall  Reinstall all plugins after uninstalling.

See code: @oclif/plugin-plugins

iop plugins uninstall [PLUGIN]

Removes a plugin from the CLI.

USAGE
  $ iop plugins uninstall [PLUGIN...] [-h] [-v]

ARGUMENTS
  [PLUGIN...]  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ iop plugins unlink
  $ iop plugins remove

EXAMPLES
  $ iop plugins uninstall myplugin

See code: @oclif/plugin-plugins

iop plugins unlink [PLUGIN]

Removes a plugin from the CLI.

USAGE
  $ iop plugins unlink [PLUGIN...] [-h] [-v]

ARGUMENTS
  [PLUGIN...]  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ iop plugins unlink
  $ iop plugins remove

EXAMPLES
  $ iop plugins unlink myplugin

iop plugins update

Update installed plugins.

USAGE
  $ iop plugins update [-h] [-v]

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Update installed plugins.

See code: @oclif/plugin-plugins

iop configure

Configure your io.Connect CLI with correct credentials.

USAGE
  $ iop configure

FLAGS
  -m, --mode=<option>  The mode to use for fetching the templates - either from a remote git repository or from an
                       embedded collection.
                       <options: auto|remote|offline>
  -t, --token=<value>  Your io.Connect Browser license key.

DESCRIPTION
  Configure your io.Connect CLI with correct credentials.

EXAMPLES
  Starts an interactive flow to configure your io.Connect CLI.

    $ iop configure

  Configures your io.Connect CLI with the provided license token.

    $ iop configure --token <license-token>

  Configures your io.Connect CLI mode to use when fetching app templates.

    $ iop configure --mode <auto-or-remote-or-offline>

  Shows help for the configure command.

    $ iop configure --help

iop help [COMMANDS]

Display help for iop.

USAGE
  $ iop help [COMMANDS] [-n]

ARGUMENTS
  COMMANDS  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for iop.

See code: @oclif/plugin-help

iop new <NEWAPP>

Bootstraps a new io.Connect app.

USAGE
  $ iop new <NEWAPP>

ARGUMENTS
  NEWAPP  The type of new app to create: browser-platform | browser-client

FLAGS
  -n, --name=<value>       The name of your IO.Connect Browser app.
  -t, --template=<option>  The IO.Connect Browser app template.
                           <options: dev-react-seed|home-react-wsp|ng|vanilla-js|wsp-frame|ng|react|vanilla-js>
  -y, --yes                Skip prompts and use default values for all options

DESCRIPTION
  Bootstraps a new io.Connect app.

EXAMPLES
  $ iop new browser-platform

  $ iop new [email protected]

  $ iop new browser-client

  $ iop new [email protected]

iop plugins

List installed plugins.

USAGE
  $ iop plugins [--json] [--core]

FLAGS
  --core  Show core plugins.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List installed plugins.

EXAMPLES
  $ iop plugins

See code: @oclif/plugin-plugins

iop plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ iop plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

FLAGS
  -f, --force    Run yarn install with force flag.
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Installs a plugin into the CLI.
  Can be installed from npm or a git url.

  Installation of a user-installed plugin will override a core plugin.

  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
  the CLI without the need to patch and update the whole CLI.


ALIASES
  $ iop plugins add

EXAMPLES
  $ iop plugins:install myplugin 

  $ iop plugins:install https://github.com/someuser/someplugin

  $ iop plugins:install someuser/someplugin

iop plugins:inspect PLUGIN...

Displays installation properties of a plugin.

USAGE
  $ iop plugins:inspect PLUGIN...

ARGUMENTS
  PLUGIN  [default: .] Plugin to inspect.

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Displays installation properties of a plugin.

EXAMPLES
  $ iop plugins:inspect myplugin

See code: @oclif/plugin-plugins

iop plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ iop plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

FLAGS
  -f, --force    Run yarn install with force flag.
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Installs a plugin into the CLI.
  Can be installed from npm or a git url.

  Installation of a user-installed plugin will override a core plugin.

  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
  the CLI without the need to patch and update the whole CLI.


ALIASES
  $ iop plugins add

EXAMPLES
  $ iop plugins:install myplugin 

  $ iop plugins:install https://github.com/someuser/someplugin

  $ iop plugins:install someuser/someplugin

See code: @oclif/plugin-plugins

iop plugins:link PLUGIN

Links a plugin into the CLI for development.

USAGE
  $ iop plugins:link PLUGIN

ARGUMENTS
  PATH  [default: .] path to plugin

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Links a plugin into the CLI for development.
  Installation of a linked plugin will override a user-installed or core plugin.

  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
  command will override the user-installed or core plugin implementation. This is useful for development work.


EXAMPLES
  $ iop plugins:link myplugin

See code: @oclif/plugin-plugins

iop plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ iop plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ iop plugins unlink
  $ iop plugins remove

iop plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ iop plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ iop plugins unlink
  $ iop plugins remove

See code: @oclif/plugin-plugins

iop plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ iop plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ iop plugins unlink
  $ iop plugins remove

iop plugins update

Update installed plugins.

USAGE
  $ iop plugins update [-h] [-v]

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Update installed plugins.

See code: @oclif/plugin-plugins