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

@boykaframework/boyka-cli

v0.11.1

Published

πŸ§‘πŸ»β€πŸ’» Command line assistant for Boyka Framework

Downloads

254

Readme

boyka-cli

Command line assistant for Boyka framework

Install

To install the assistant, run the following command on the terminal:

npm i -g @boykaframework/boyka-cli

Commands

boyka doctor

This command will check whether your machine setup for Boyka Framework is done properly or not.

If there is any problem in the setup, the assistant will accordingly suggest solution to fix the problem.

boyka init [name]

This will create Maven project on your machine along with the config file for Boyka Framework.

This will also add sample tests for API, Web, Android and iOS applications.

boyka configure init --path /path/to/config

This command will create a basic Boyka-framework config file named boyka-config.json at the specified path.

If the optional --path option is not provided, it will create the config at src/test/resources folder by default.

boyka configure api [name] --path /path/to/config

This will add API configuration in the config file with the given name to the config block.

This will ask a set of questions to the user and depending on their answers, it will configure the API config.

If the default config path is not src/test/resources, then you can set the config path by using the optional param of --path <path/to/config>.

boyka configure web [name] --path /path/to/config

This will add Web configuration in the config file with the given name to the config block.

This will ask a set of questions to the user and depending on their answers, it will configure the Web config.

If the default config path is not src/test/resources, then you can set the config path by using the optional param of --path <path/to/config>.

boyka configure android [name] --path /path/to/config

This will add Mobile Android configuration in the config file with the given name to the config block.

This will ask a set of questions to the user and depending on their answers, it will configure the Mobile config.

If the default config path is not src/test/resources, then you can set the config path by using the optional param of --path <path/to/config>.

boyka configure ios [name] --path /path/to/config

This will add Mobile iOS configuration in the config file with the given name to the config block.

This will ask a set of questions to the user and depending on their answers, it will configure the Mobile config.

If the default config path is not src/test/resources, then you can set the config path by using the optional param of --path <path/to/config>.