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

leadent-config-manager-beta

v0.0.25

Published

Leadent Config Manager CLI

Downloads

5

Vulnerabilities

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

Links

Git

Maintainers

gabiras12gabiras12

Keywords

oclif

Readme

oclif-hello-world

oclif example Hello World CLI

oclif Version CircleCI Downloads/week License

Usage

$ npm install -g leadent-config-manager-beta
$ leadent-config-manager COMMAND
running command...
$ leadent-config-manager (--version)
leadent-config-manager-beta/0.0.24 darwin-x64 node-v14.21.3
$ leadent-config-manager --help [COMMAND]
USAGE
  $ leadent-config-manager COMMAND
...

Commands

leadent-config-manager hello PERSON

Say hello

USAGE
  $ leadent-config-manager hello [PERSON] -f <value>

ARGUMENTS
  PERSON  Person to say hello to

FLAGS
  -f, --from=<value>  (required) Who is saying hello

DESCRIPTION
  Say hello

EXAMPLES
  $ oex hello friend --from oclif
  hello friend from oclif! (./src/commands/hello/index.ts)

See code: dist/commands/hello/index.ts

leadent-config-manager hello:world

Say hello world

USAGE
  $ leadent-config-manager hello:world

DESCRIPTION
  Say hello world

EXAMPLES
  $ leadent-config-manager hello:world
  hello world! (./src/commands/hello/world.ts)

See code: dist/commands/hello/world.ts

leadent-config-manager help [COMMANDS]

Display help for leadent-config-manager.

USAGE
  $ leadent-config-manager help [COMMANDS] [-n]

ARGUMENTS
  COMMANDS  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for leadent-config-manager.

See code: @oclif/plugin-help

leadent-config-manager plugins

List installed plugins.

USAGE
  $ leadent-config-manager plugins [--core]

FLAGS
  --core  Show core plugins.

DESCRIPTION
  List installed plugins.

EXAMPLES
  $ leadent-config-manager plugins

See code: @oclif/plugin-plugins

leadent-config-manager plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ leadent-config-manager plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

FLAGS
  -f, --force    Run yarn install with force flag.
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Installs a plugin into the CLI.
  Can be installed from npm or a git url.

  Installation of a user-installed plugin will override a core plugin.

  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
  the CLI without the need to patch and update the whole CLI.


ALIASES
  $ leadent-config-manager plugins:add

EXAMPLES
  $ leadent-config-manager plugins:install myplugin 

  $ leadent-config-manager plugins:install https://github.com/someuser/someplugin

  $ leadent-config-manager plugins:install someuser/someplugin

leadent-config-manager plugins:inspect PLUGIN...

Displays installation properties of a plugin.

USAGE
  $ leadent-config-manager plugins:inspect PLUGIN...

ARGUMENTS
  PLUGIN  [default: .] Plugin to inspect.

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Displays installation properties of a plugin.

EXAMPLES
  $ leadent-config-manager plugins:inspect myplugin

See code: @oclif/plugin-plugins

leadent-config-manager plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ leadent-config-manager plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

FLAGS
  -f, --force    Run yarn install with force flag.
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Installs a plugin into the CLI.
  Can be installed from npm or a git url.

  Installation of a user-installed plugin will override a core plugin.

  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
  the CLI without the need to patch and update the whole CLI.


ALIASES
  $ leadent-config-manager plugins:add

EXAMPLES
  $ leadent-config-manager plugins:install myplugin 

  $ leadent-config-manager plugins:install https://github.com/someuser/someplugin

  $ leadent-config-manager plugins:install someuser/someplugin

See code: @oclif/plugin-plugins

leadent-config-manager plugins:link PLUGIN

Links a plugin into the CLI for development.

USAGE
  $ leadent-config-manager plugins:link PLUGIN

ARGUMENTS
  PATH  [default: .] path to plugin

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Links a plugin into the CLI for development.
  Installation of a linked plugin will override a user-installed or core plugin.

  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
  command will override the user-installed or core plugin implementation. This is useful for development work.


EXAMPLES
  $ leadent-config-manager plugins:link myplugin

See code: @oclif/plugin-plugins

leadent-config-manager plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ leadent-config-manager plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ leadent-config-manager plugins:unlink
  $ leadent-config-manager plugins:remove

leadent-config-manager plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ leadent-config-manager plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ leadent-config-manager plugins:unlink
  $ leadent-config-manager plugins:remove

See code: @oclif/plugin-plugins

leadent-config-manager plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ leadent-config-manager plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ leadent-config-manager plugins:unlink
  $ leadent-config-manager plugins:remove

leadent-config-manager plugins:update

Update installed plugins.

USAGE
  $ leadent-config-manager plugins:update [-h] [-v]

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Update installed plugins.

See code: @oclif/plugin-plugins

leadent-config-manager setup-frontend

Fetch configuration base files and merge with client specific files stored in the config repo.

USAGE
  $ leadent-config-manager setup-frontend -c <value> -e <value> [-i <value>]

FLAGS
  -c, --client=<value>       (required) Client name (folder name in the config repo)
  -e, --environment=<value>  (required) Targeted environment (e.g.: dev, local, staging, production)
  -i, --inherit=<value>      An environment to be merged with the base file before merging with the targeted environment

DESCRIPTION

  Fetch configuration base files and merge with client specific files stored in the config repo.
  It has a default config and override with the client specific config.
  We also have per environment configuration.

  E.g.: Configuration Repo:
  - base/frontend/src/config/config.js
  - base/frontend/src/lang/en.json
  - client1/production/frontend/src/config/config.js
  - client1/production/frontend/src/lang/en.json

  If you run:

  $ leadent-config-manager-beta setup-frontend -c client1 -e production

  It will merge the base one with the production one for the specified client and output the following files:

  - src/config/config.js
  - src/lang/en.json

  Obs. The output files are relative to the root of the remote config repository you are pointing to.
  That means that what defines the output files is the structure of the config folder, not the script itself.
  If you, for example, remove the 'src/' folder from the config repo, the output files will not contain it as well.


EXAMPLES
  $ leadent-config-manager-beta setup-frontend -c client1 -e production

  $ leadent-config-manager-beta setup-frontend -c client1 -e local -i staging

See code: dist/commands/setup-frontend.ts

leadent-config-manager setup-portal

Fetch configuration base files and merge with client specific files stored in the config repo.

USAGE
  $ leadent-config-manager setup-portal -c <value> -e <value> [-i <value>]

FLAGS
  -c, --client=<value>       (required) Client name (folder name in the config repo)
  -e, --environment=<value>  (required) Targeted environment (e.g.: dev, local, staging, production)
  -i, --inherit=<value>      An environment to be merged with the base file before merging with the targeted environment

DESCRIPTION

  Fetch configuration base files and merge with client specific files stored in the config repo.
  It has a default config and override with the client specific config.
  We also have per environment configuration.

  E.g.: Configuration Repo:
  - base/portal/src/config/config.js
  - base/portal/src/lang/en.json
  - base/portal/src/sass/leadent.scss
  - client1/production/portal/src/config/config.js
  - client1/production/portal/src/lang/en.json
  - client1/production/portal/src/sass/leadent.scss

  If you run:

  $ leadent-config-manager-beta setup-portal -c client1 -e production

  It will merge the base one with the production one for the specified client and output the following files:

  - src/config/config.js
  - src/lang/en.json
  - src/sass/leadent.scss

  Obs. The output files are relative to the root of the remote config repository you are pointing to.
  That means that what defines the output files is the structure of the config folder, not the script itself.
  If you, for example, remove the 'src/' folder from the config repo, the output files will not contain it as well.


EXAMPLES
  $ leadent-config-manager-beta setup-portal -c client1 -e production

  $ leadent-config-manager-beta setup-portal -c client1 -e local -i staging

See code: dist/commands/setup-portal.ts