@mikeburr/sfdx-repl
a simple REPL for the Salesforce CLI (Salesforce DX)
Last updated a month ago by mikeburr .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install @mikeburr/sfdx-repl 
SYNC missed versions from official npm registry.

sfdx-repl

a simple REPL for the Salesforce CLI (Salesforce DX)

Version CircleCI Appveyor CI Codecov Greenkeeper Known Vulnerabilities Downloads/week License

$ npm install -g @mikeburr/sfdx-repl
$ @mikeburr/sfdx-repl COMMAND
running command...
$ @mikeburr/sfdx-repl (-v|--version|version)
@mikeburr/sfdx-repl/0.1.0 darwin-x64 node-v11.12.0
$ @mikeburr/sfdx-repl --help [COMMAND]
USAGE
  $ @mikeburr/sfdx-repl COMMAND
...

@mikeburr/sfdx-repl repl:repl [-e <string>] [--help <help>] [-v <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal]

runs an SFDX REPL

USAGE
  $ @mikeburr/sfdx-repl repl:repl [-e <string>] [--help <help>] [-v <string>] [-u <string>] [--apiversion <string>] 
  [--json] [--loglevel trace|debug|info|warn|error|fatal]

OPTIONS
  -e, --execute=execute                            command to be executed
  -u, --targetusername=targetusername              username or alias for the target org; overrides default target org
  -v, --targetdevhubusername=targetdevhubusername  username or alias for the dev hub org; overrides default dev hub org
  --apiversion=apiversion                          override the api version used for api requests made by this command
  --help                                           show CLI help
  --json                                           format output as json
  --loglevel=(trace|debug|info|warn|error|fatal)   [default: warn] logging level for this command invocation

EXAMPLES
  $ sfdx repl:repl --targetusername me@example.com
  me@example.com> 

  $ sfdx repl:repl -e "1 + 2"
  3

  Note that many interactions with Salesforce will return JavaScript Promises, which
  can be difficult to work with in an interactive environment. Use --experimental-repl-await
  to make things a bit easier:

  $ NODE_OPTIONS=--experimental-repl-await sfdx repl:repl -u me@example.com
  me@example.com> (await $conn.identity()).username
  'me@example.com'

See code: src/commands/repl/repl.ts

@mikeburr/sfdx-repl repl:script [-v <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal]

runs a script using the SFDX REPL

USAGE
  $ @mikeburr/sfdx-repl repl:script [-v <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel 
  trace|debug|info|warn|error|fatal]

ARGUMENTS
  SCRIPT  filename of script to run

OPTIONS
  -u, --targetusername=targetusername              username or alias for the target org; overrides default target org
  -v, --targetdevhubusername=targetdevhubusername  username or alias for the dev hub org; overrides default dev hub org
  --apiversion=apiversion                          override the api version used for api requests made by this command
  --json                                           format output as json
  --loglevel=(trace|debug|info|warn|error|fatal)   [default: warn] logging level for this command invocation

EXAMPLES
  $ sfdx repl:repl --targetusername me@example.com
  me@example.com> 

  $ sfdx repl:repl -e "1 + 2"
  3

  Note that many interactions with Salesforce will return JavaScript Promises, which
  can be difficult to work with in an interactive environment. Use --experimental-repl-await
  to make things a bit easier:

  $ NODE_OPTIONS=--experimental-repl-await sfdx repl:repl -u me@example.com
  me@example.com> (await $conn.identity()).username
  'me@example.com'

See code: src/commands/repl/script.ts

Debugging your plugin

We recommend using the Visual Studio Code (VS Code) IDE for your plugin development. Included in the .vscode directory of this plugin is a launch.json config file, which allows you to attach a debugger to the node process when running your commands.

To debug the hello:org command:

  1. Start the inspector

If you linked your plugin to the sfdx cli, call your command with the dev-suspend switch:

$ sfdx hello:org -u myOrg@example.com --dev-suspend

Alternatively, to call your command using the bin/run script, set the NODE_OPTIONS environment variable to --inspect-brk when starting the debugger:

$ NODE_OPTIONS=--inspect-brk bin/run hello:org -u myOrg@example.com
  1. Set some breakpoints in your command code
  2. Click on the Debug icon in the Activity Bar on the side of VS Code to open up the Debug view.
  3. In the upper left hand corner of VS Code, verify that the "Attach to Remote" launch configuration has been chosen.
  4. Hit the green play button to the left of the "Attach to Remote" launch configuration window. The debugger should now be suspended on the first line of the program.
  5. Hit the green play button at the top middle of VS Code (this play button will be to the right of the play button that you clicked in step #5).

    Congrats, you are debugging!

Current Tags

  • 0.1.0                                ...           latest (a month ago)

2 Versions

  • 0.1.0                                ...           a month ago
  • 0.0.1                                ...           2 months ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 27
Dependents (0)
None

Copyright 2014 - 2016 © taobao.org |