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

cumulocity-tools

v2.1.24

Published

Tools to work with cumulocity UI.

Downloads

13

Readme

UI developer command line tools

Usage

c8y [options] [command]

Options

    -V, --version                                    output the version number
    -s, --searchSibling [siblingsPath]               Load application manifests and plugins from sibling folders. A specific path supporting globs can also be used.
    -b, --buildPath <buildPath>                      The file system path to load a build from
    -t, --target <target>                            The target file to be used. Can be either a relative file path to json. Or a the name of the target to be read at ./targets/<target>.json
    -u, --url <url>                                  The url of the remote instance.
    -h, --help                                       output usage information

Commands

    server [options]                                 Run local development server
    install [package]                                Install a Cumulocity UI package using npm.
    create:plugin <pluginName>                       Create plugin folder with a manifest inside
    create:app <appName>                             Creates a new json manifest file for the app
    build:plugin <pluginContextPath> [outputDir]     Build the specified plugin and create a zip file
    build:app [appContextPath] [outputDir]           Build the specified app and create a zip file. If appContextPath if ommited it will read the contextPath of the json manifest file.
    build:target <targetNameOrFilePath> [outputDir]  Assembles all the apps for the specified target file
    deploy:app [options] [appContextPath]            Deploy the app with the specified contextPath. If appContextPath is ommited it will read the contextPath of the json manifest file.
    deploy:target [options] [targetNameOrFilePath]   Deploy all the apps specified in the target file
    locale:extract [outputDir]                       Extract all the strings for translation and outputs the .po files to defined folder.
    locale:update <poFilesPath>                      Reads translation (.po) from the specifed <poFilesPath> and updates all the plugins with the available information.
    util:showimports <appContextPath>                List the lists of imports for a specific application