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

pekora-cli

v0.0.15

Published

I want to go home faster

Readme

pekora-cli

I want to go home faster

What the hell is this?

Auto generate di container and frontline mapping source based on this module

This is first version of program. So, there will be many bugs.

Install

npm i --save-dev pekora-cli
# or
npm i -g pekora-cli

How to use?

                 _                                            _   _
  _ __     ___  | | __   ___    _ __    __ _            ___  | | (_)
 | '_ \   / _ \ | |/ /  / _ \  | '__|  / _` |  _____   / __| | | | |
 | |_) | |  __/ |   <  | (_) | | |    | (_| | |_____| | (__  | | | |
 | .__/   \___| |_|\_\  \___/  |_|     \__,_|          \___| |_| |_|
 |_|
Usage: peko [options]

CLI for auto generate di.container.js and frontline.js

---Example---

- Generate di.container.js and frontline.js
peko -od ./sample/di.container.js -of ./sample/frontline.ts -s ./sample/**/*.js ./sample/test.js

Options:
  -V, --version                     output the version number
  -od, --output-di <string>         Output path of di container (overwrite). ex) /path/to/filename.js
  -of, --output-frontline <string>  Output path of frontline (overwrite). ex) /path/to/filename.js
  -s, --source <strings...>         Directory of source. You can use wild card and mulitiple paths ex) /path/**/*.js /other/path/*.js
  -h, --help                        display help for command

In your source should be...

//@Autowired        <-- Should mark autowired annotation so that generate in di.container.js
class Foo {
   /**
   * @param {Index1Controller} index1Controller         <-- Should write params so that binding dependency in di.container.js
   * @param {Index2Controller} index2Controller
   */
   constructor(index1Controller, index2Controller) {
        this.index1Controller = index1Controller;
        this.index2Controller = index2Controller;
   }

   //@frontline             <-- Should mark frontline annotation so that generate in frontline.js
   bar(a, b, c) {

   }
}

//@Autowired
class Foo2 {

}
//--boundary                <-- If you use non-constructor class, then should mark end of class using //--boundary

Test run

npm run build
./bundle/out.js -od ./sample/di.container.js -of ./sample/frontline.ts -s ./sample/**/*.js ./sample/test.js;
npm run build:frontline