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

@fujia/cli-core

v1.5.2

Published

cli core

Downloads

3

Vulnerabilities

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

Links

Git

Maintainers

sunnyfusunnyfu

Keywords

Readme

A cli tools making application development simple and powerful.

English | 简体中文

Introduction

stage are open source and aim at helping to develop, build and deploy various of applications quickly for individual developers or freelancer cli tools. It built in many default templates which can resolve general requests and are improving and extending. what's more, it's supported by customized templates.

Getting started

  1. installation:
npm install -g @fujia/cli-core

Features

  • Initializing a project and launching it quickly by using a template, some common best practices are added in the template.
  • Abundant default templates and customizable support.
  • Initializing git repo automatically.
  • Releasing a npm package simply and correctly.
  • Efficiently build a docker image locally then push to container mirror repository and you own servers automatically.
  • Easily deploy or update an application(service) based on docker swarm or PM2.
  • Friendly to individual developers.

Usage

🔗 view all commands and options：


stage -h

# Usage: stage <command> [options]
#
# Options:
#   -v, --version                 output the version number
#   -d, --debug                   enable debug model (default: false)
#   -lp, --localPath <localPath>  specify the local debug file path (default: "")
#   -h, --help                    display help for command
#
# Commands:
#   init [options] [projectName]  initializing an universal project quickly
#   publish [options]             publish a project
#   release [options]             release a npm package
#   docker [options]              to build a docker image and update corresponding service
#   service                       deploy or update a service
#   clean [cacheFileName]         clean caches
#   help [command]                display help for command

Environments Description

  1. The command of "stage docker" and "stage service" are depended on docker environment, makes sure the related commands are run correctly, you have to configure the docker in local host and the server. How to install docker? please consults: https://docs.docker.com/get-docker/.

  2. Running the command of "stage service", if you selected the PM2 to manage your services(applications), you have to configure node environment and install package of PM2 globally in the server. we recommend to manage node version by using nvm. How to install nvm? please consults: https://github.com/nvm-sh/nvm.

installing pm2 globally:


npm install -g pm2

Head over to the docs of PM2(https://pm2.keymetrics.io/docs/usage/quick-start/).

  1. Before any commands are run, stage will check user home directory of local host. If don't exist, it'll throw exceptions and end the process.

  2. when some commands are run, stage will create a directory which named ".stage-cli" in the user home directory.

Options

-v,--version：view stage version

enter the following command：

stage -v
# 1.3.6

-d, --debug：enable debug mode, by default：false

You can enable debug mode when you want to check the running details or development. If enabled, it will print the execution flows and key parameters information in the internal.

take the clean command as an example：

stage -d clean

# [stage] verb [cli-exec]
# [stage] verb [cli-exec]     localPath: undefined,
# [stage] verb [cli-exec]     pkgName: @fujia/cli-clean,
# [stage] verb [cli-exec]     cmdName: clean
# [stage] verb [cli-exec]
# [stage] verb localPath /Users/sunny/.stage-cli/caches
# [stage] verb storeDir /Users/sunny/.stage-cli/caches/node_modules
# [stage] verb [cli-package]
# [stage] verb [cli-package]       localPath: /Users/sunny/.stage-cli/caches
# [stage] verb [cli-package]       pkgName: @fujia/cli-clean
# [stage] verb [cli-package]       pkgVersion: latest
# [stage] verb [cli-package]       storeDir: /Users/sunny/.stage-cli/caches/node_modules
# [stage] verb [cli-package]
# [stage] verb [cli-package]
# [stage] verb [cli-package] The version of installing package is: 1.3.6
# [stage] verb [cli-package] Starting install @fujia/cli-clean...
# ...

-lp, --localPath ：specify local path of the command when in development or debug mode

In development or debug mode, you can add the parameter: --localPath , then it will use local npm package to execute the corresponding command.

for example：

stage -d -lp [workDir]/stage/commands/cli-clean clean

# [stage] verb [cli-exec]
# [stage] verb [cli-exec]     localPath: undefined,
# [stage] verb [cli-exec]     pkgName: @fujia/cli-clean,
# [stage] verb [cli-exec]     cmdName: clean
# ...

-h, --help：views help information

seeing above.

Commands

You can initialize, deploy and update an application(service) by series of commands.

init [options] [projectName]：to initialize a general project quickly

  1. view init command:
stage help init

# Usage: stage init [options] [projectName]
#
# initializing an universal project quickly
#
# Options:
#   -f, --force  force to init project
#   -h, --help   display help for command
  1. -f, --force, by default: false

when you passed this parameter, it'll force to initialize a project even if the work directory is not empty.

Note: this is a very dangerous operation of remove one folder. so "stage" will confirm again and check the removed folder name before remove.

  1. projectName
  • optional, if don't pass or invalid, you have to re-enter and "stage" will verify it. Note that the name follow the same rules as npm package name and strongly recommended don't use special characters.
  1. select a template type, support the following:
  • default: built in template, maintained by "stage" terms.
  • custom: use your own templates
  1. the available default templates, as follows:

tips: most of templates are in the stage of development, we will improve them as soon as possible.

web:

app:

  • react-native: base on React Native
  • electron-rect: combine ui-puzzles@rect with Electron
  • electron-antd: combine Antd with Electron

library:

  • rollup: base on the Rollup
  • webpack: base on the webpack

mini-program:

  • wechat：wechat's mini program
  • alipay：alipay's mini program

In the templates, we will add some common best practices, as: husky, Dockerfile and hot update of electron etc. of cause, you can remove them as your like. we hope that you can pay more attention to the business and ideas, producing the product of MVP1.0 quickly.

  1. we also provide a way to initial project which more simple, as follows:
npm init stage@latest demos

That all, enjoy your works.

publish [options]：push your project to the github or gitee

this functionality is not perfect and we are planing to refactor it.

  1. views the command：

stage help publish

# Usage: stage publish [options]
#
# publish a project
#
# Options:
#   --refreshRepo   force to update the remote Git repository
#   --refreshToken  force to update the token of remote repository
#   --refreshOwner  force to update the type of remote repository
#   -h, --help      display help for command
  1. options: --refreshRepo、--refreshToken、--refreshOwner
  • --refreshRepo：force to update remote git repo
  • --refreshToken：force to refresh remote git token
  • --refreshOwner：force to update remote repository type(individual or organization)
  1. input git repo token

running the command first, you need to enter Git token, and stage will store the token in .stage-cli folder.

How to set token?

  • Github - seeing：https://github.com/settings/tokens
  • Gitee - seeing：https://gitee.com/profile/personal_access_tokens
  1. if the token is right, stage will finish the following operations automatically:
  • initialize git and add default .gitignore file(Note: this .gitignore file only adjust to npm projects)
  • add remote git url and create a main branch
  • commit the initial template code to main branch, then check out the feature/0.1.0 branch

Note: stage will make some checks before running the command, as: check if the project is a valid npm project.

release [options]：publish a npm package easily

You only need to select a sematic version and publish it to npm registry quickly.

  1. view the command:

stage help release

# Usage: stage release [options]
#
# release a npm package
#
# Options:
#   -a, --access <publishAccess>  set publish access is true (default: "public")
#   -h, --help                    display help for command
  1. to ensure that the project is completely and correctly published to the npm, the following checks are done before publishing:
  • check if is a npm project
  • check for the existence of a files field in package.json or a .gitignore file in the project root, if they are not exist, stage will throw exceptions then end the process
  • check the npm registry, if you have used the other registry mirror as: taobao, stage will force to switch to official registry by executing "npx nrm use npm"
  • check if you are logged in to npm, if not, you'll be prompted to do so
  1. at last, select a sematic version and start publishing.

that all, we published a npm package simply and correctly.

docker [options]：to build a docker image locally and push to container mirror repository

  1. view the command:

stage help docker


# Usage: stage docker [options]
#
# to build a docker image and update corresponding service
#
# Options:
#   -b, --build                        build a docker image (default: false)
#   -u, --updateService [serviceName]  update a service
#   -h, --help                         display help for command
  1. the options: -b, --build and -u, --updateService [serviceName]
  • -b,--build：build a docker image locally and push to the container mirror repository if build successful, then stage will log in to the server by ssh and pull the latest built image
  • -u, --updateService [serviceName]：it's optional, but if you set the parameter, stage will update the corresponding service when the remote server pull the latest image.
  1. stage will check the following items before build:
  • check docker environment. Note: stage don't install the docker automatically and only prompt that
    • check if exist Dockerfile file in the project root
    • check if exist .dockerignore file in the project root
  • check the current branch name is "main" or "master", Note: stage only you build a docker image in main or master branch
  • check the git stash of current project is empty
  1. enter the server information, includes: username, port, ip.

the server information will store to the server-info.json file in the .stage-cli folder. the purpose of this is to void entering the same things repetitively. Note: this information is sensitive, please keep it safe!

  1. enter the container mirror repo information, the details includes:
  • owner: username
  • userPwd: password
  • repoZone: repo zone
  • repoNamespace: namespace
  • mirrorName: mirror name(repo name)
  • mirrorVersion?: mirror version

we recommend to use the free container mirror service provide by aliyun or tencent.

service：deploy or update a service(application)

  1. view the command:

stage help service

# Usage: stage service [options] [command]
#
# deploy or update a service
#
# Options:
#   -h, --help                    display help for command
#
# Commands:
#   deploy [stackName] [workDir]  deploy a service via docker image or PM2
#   update [serviceName]          update a service via docker image
#   help [command]                display help for command
  1. deploy a service via docker swarm

stage assumes you have configured docker swarm in the server. seeing here: https://docs.docker.com/engine/swarm/stack-deploy/.

use the following command:


docker service deploy stack-name
  1. deploy or manage a service via PM2

stage assumes you have installed the PM2 globally, seeing here: https://pm2.keymetrics.io/docs/usage/quick-start/.


docker service deploy

clean [cacheFileName]：clean up caches

You can clean up the cached npm packages manually.

  1. view the command:

stage help clean

# Usage: stage clean [options] [cacheFileName]
#
# clean caches
#
# Options:
#   -h, --help  display help for command
  1. examples:

stage clean


# ✔ Installed 1 packages
# ✔ Linked 34 latest versions
# ✔ Run 0 scripts
# ✔ All packages installed (34 packages installed from npm registry, used 5s(network 5s), speed 299.45KB/# s, json 34(1.57MB), tarball 0B)
# [stage] info starting to clean cached directories: /Users/sunny/.stage-cli/caches, /Users/sunny/.# stage-cli/templates
# [stage] info process exited!

help [command]：view the usage of one command.

Examples

we have provided a complete example to demonstrate how to create a web application so that you can quickly understand the entire process. go to.

Questions

stage is available now, but still under rapid development, so there are many problems, please believe that we will actively work on them!

Testing

unit tests, to ensure the high availability, stability and maintainability of the application, we must ensure sufficient unit testing.

Plans

Template Ecological Construction

  1. to refine the default templates.

  2. to determine the development direction of custom templates.

More useful features

  1. support chinese.

  2. commands plugged in, which is the focus of the next big release.

  3. cloud build.

Combining the power of third-party developers

this is the focus and direction of the future development of the stage.

Supporting Stage

if the project is helpful to you, please click a star on github, thanks so much.

References

  1. Gitee OpenAPI - https://gitee.com/api/v5/swagger#/getV5ReposOwnerRepoStargazers?ex=no.

  2. docker docs - https://docs.docker.com/get-docker/.

  3. nvm - https://github.com/nvm-sh/nvm.

  4. pm2 - https://pm2.keymetrics.io/docs/usage/quick-start/.

  5. vue-element-admin - (https://panjiachen.github.io/vue-element-admin-site/zh/guide/).

  6. Container mirror service of aliyun(ACR) - https://help.aliyun.com/document_detail/257112.html

  7. Container mirror service of tencent - https://cloud.tencent.com/document/product/1141.

  8. node.js - https://nodejs.org/en/docs/.

  9. npm docs - https://docs.npmjs.com/.

  10. imooc-cli - https://github.com/imooc-lego/imooc-cli.