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 🙏

© 2025 – Pkg Stats / Ryan Hefner

sfdx-djc-plugin

v0.0.32

Published

Testing

Downloads

39

Vulnerabilities

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

Links

Git

Maintainers

djcarrolldjcarroll

Keywords

sfdx-plugin

Readme

sfdx-djc-plugin Build Status

Version License

  • [sfdx-djc-plugin Build Status](#sfdx-djc-plugin--build-statushttpstravis-ciorgdcarrollsfdx-djc-pluginsvgbranchmasterhttpstravis-ciorgdcarrollsfdx-djc-plugin)

A plugin for the Salesforce CLI built by Dave Carroll and containing a few of helpful commands.

Setup

Install from source

  1. Install the SDFX CLI.

  2. Clone the repository: git clone [email protected]:wadewegner/sfdx-djc-plugin.git

  3. Install npm modules: yarn

  4. Link the plugin: sfdx plugins:link .

Install as plugin

  1. Install plugin: sfdx plugins:install sfdx-tohoom-plugin
$ npm install -g djc-plugin
$ djc-plugin COMMAND
running command...
$ djc-plugin (-v|--version|version)
djc-plugin/0.0.32 darwin-x64 node-v14.15.0
$ djc-plugin --help [COMMAND]
USAGE
  $ djc-plugin COMMAND
...

djc-plugin djc:cleardata -o <string> [-v <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

Delete data from a scratch org.

USAGE
  $ djc-plugin djc:cleardata -o <string> [-v <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel 
  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

OPTIONS
  -o, --sobject=sobject                                                             (required) Object to delete all
                                                                                    records for

  -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|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
                                                                                    this command invocation

EXAMPLE
  $ sfdx djc:cleardata -o Account

See code: src/commands/djc/cleardata.ts

djc-plugin djc:export [-v <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

Import data to an org to use in a scratch org.

USAGE
  $ djc-plugin djc:export [-v <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel 
  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

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|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
                                                                                    this command invocation

EXAMPLE
  $ sfdx djc:import -p directory

See code: src/commands/djc/export.ts

djc-plugin djc:import [-x] [-v <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

Import data to an org to use in a scratch org.

USAGE
  $ djc-plugin djc:import [-x] [-v <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel 
  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

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

  -x, --xfiles                                                                      Use the limited size files instead
                                                                                    of full size files

  --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|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
                                                                                    this command invocation

EXAMPLE
  $ sfdx djc:import -p directory

See code: src/commands/djc/import.ts

djc-plugin tohoom:data:export -o <string> -t <string> [-n <string>] [-m <integer>] [-s] [-p] [-e] [-b] [-k] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

Extract data from an org to use in a scratch org. Just supply a list of SObjects and you should end up with a dataset and data plan that can be used with the official force:data:tree:import command

USAGE
  $ djc-plugin tohoom:data:export -o <string> -t <string> [-n <string>] [-m <integer>] [-s] [-p] [-e] [-b] [-k] [-u 
  <string>] [--apiversion <string>] [--json] [--loglevel 
  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

OPTIONS
  -b, --preserveobjectorder                                                         If present, uses the order of the
                                                                                    objects from the command to
                                                                                    determine plan order

  -e, --enforcereferences                                                           If present, missing child reference
                                                                                    cause the record to be deleted,
                                                                                    otherwise, just the reference field
                                                                                    is removed

  -k, --tohoom                                                                      Special Tohoom processing to handle
                                                                                    self referential relationship

  -m, --maxrecords=maxrecords                                                       [default: 10] Max number of records
                                                                                    to return in any query

  -n, --planname=planname                                                           [default: new-data-plan] name of the
                                                                                    data plan to produce, deflaults to
                                                                                    "new-plan"

  -o, --objects=objects                                                             (required) Comma separated list of
                                                                                    objects to fetch

  -p, --spiderreferences                                                            Include refereced SObjects
                                                                                    determined by schema examination and
                                                                                    existing data

  -s, --savedescribes                                                               Save describe results (for
                                                                                    diagnostics)

  -t, --targetdir=targetdir                                                         (required) target directoy to place
                                                                                    results in

  -u, --targetusername=targetusername                                               username or alias for the target
                                                                                    org; overrides default target 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|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
                                                                                    this command invocation

EXAMPLE
  $ sfdx tohoom:data:export -o Account,Contact,Case,Opportunity -t data/exported -n my-testplan

See code: src/commands/tohoom/data/export.ts

djc-plugin tohoom:data:split [-n <string>] [-v <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

Extract data from an org to use in a scratch org. Just supply a list of SObjects and you should end up with a dataset and data plan that can be used with the official force:data:tree:import command

USAGE
  $ djc-plugin tohoom:data:split [-n <string>] [-v <string>] [--apiversion <string>] [--json] [--loglevel 
  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

OPTIONS
  -n, --planname=planname                                                           [default: data-plan] name of the
                                                                                    data plan to use with split

  -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|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
                                                                                    this command invocation

EXAMPLE
  $ sfdx tohoom:data:export -o Account,Contact,Case,Opportunity -t data/exported -n my-testplan

See code: src/commands/tohoom/data/split.ts