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

@komaci/cli

v248.1.10

Published

CLI utility that enables developers to use komaci from the command line.

Downloads

81

Readme

@komaci/cli

CLI tool to test out functionality for komaci. Currently supports only one command, modgen.

modgen Command

This command will generate a komaci module, similar to what komaci-tester did, but with some improvements. Some example components can be found in ./sandbox.

One important difference is that the component's namespace is no longer hardcoded to "c". It will now be derived from the module structure. For instance;

sandbox
├── jsconfig.json
└── modules              // LWC 'modules' directory; not required
    ├── c                // "c" is the namespace for the modules within this directory
    │   └── komaciAction // "lightning/komaciAction" component — komaciAction in the "c" namespace
    └── lightning        // "lightning" is the namespace for the modules below
        ├── komaciAction // "lightning/komaciAction" component — Same as c/komaciAction, but in a trusted namespace
        └── recordForm   // "lightning/recordForm" component — copied from ui-lightning-components

Usage

Run the following from the packages/@komaci/cli directory:

yarn
yarn build
# Run modgen on the component defined @ <path>
yarn komaci modgen <path>

Examples

# Run modgen on c/komaciAction:
yarn komaci modgen sandbox/modules/c/komaciAction
# Print only the lwc metadata for c/komaciAction:
yarn komaci modgen sandbox/modules/c/komaciAction --only lwc

Modgen can also take in a list of paths:

yarn komaci modgen sandbox/modules/lightning/komaciAction sandbox/modules/lightning/recordForm

If all the modules are in the same subdirectory, you can use a glob pattern:

# Run modgen on all modules in the lightning namespace:
yarn komaci modgen sandbox/modules/lightning/*
# Run modgen on all modules in all namespaces:
yarn komaci modgen sandbox/modules/*/*