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

@salesforce/plugin-source

v3.3.5

Published

Commands to interact with source formatted metadata

Downloads

613,595

Vulnerabilities

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

Links

Git

Maintainers

dme722dme722nolanlawsonnolanlawsonire-npm-team-userire-npm-team-userjburniejburnieabirchfieldsfdcabirchfieldsfdcdlouvtondlouvtonmobifymobifyjmsjtujmsjtujasonschroeder-sfdcjasonschroeder-sfdcpackagellamapackagellamamawardmawarddanielshoxdanielshoxduane.chewduane.chewdferrodferrojcourtnerjcourtnerjye-sfjye-sfadirasanamadirasanamhkiihkiiiamaziziamazizdbreese-salesforcedbreese-salesforceashokrudrarajuashokrudrarajudhersamdhersamdemianbrechtdemianbrechtmbettiombettiodamilareolowoniyidamilareolowoniyimmadialaganmmadialaganmjrustmjrustsalesforce-releasessalesforce-releasesmpsennmpsennkevinv11nkevinv11nbyaobyaopmdartuspmdartusekashidaekashidagr8gatsbygr8gatsbyravi.jayaramapparavi.jayaramappaapapkoapapkojleen-sfdcjleen-sfdcjqianjqiancwallsfcwallsfdhagberg-sfdhagberg-sfkhawkinskhawkinsamphroamphrojodarovejodarovesfdctakasfdctakafernomacfernomacjimjagjimjagivarleyivarleyjbartolotta-sfdcjbartolotta-sfdc

Keywords

forcesalesforcesalesforcedxsfsf-pluginsfdxsfdx-plugin

Readme

plugin-source

NPM Downloads/week License

Commands for interacting with metadata in Salesforce orgs.

This plugin is bundled with the Salesforce CLI. For more information on the CLI, read the getting started guide.

We always recommend using the latest version of these commands bundled with the CLI, however, you can install a specific plugin version or tag if needed.

Install

sfdx plugins:install [email protected]

Issues

Please report any issues at https://github.com/forcedotcom/cli/issues

Contributing

  1. Please read our Code of Conduct
  2. Create a new issue before starting your project so that we can keep track of what you are trying to add/fix. That way, we can also offer suggestions or let you know if there is already an effort in progress.
  3. Fork this repository.
  4. Build the plugin locally
  5. Create a topic branch in your fork. Note, this step is recommended but technically not required if contributing using a fork.
  6. Edit the code in your fork.
  7. Write appropriate tests for your changes. Try to achieve at least 95% code coverage on any new code. No pull request will be accepted without unit tests.
  8. Sign CLA (see CLA below).
  9. Send us a pull request when you are done. We'll review your code, suggest any needed changes, and merge it in.

CLA

External contributors will be required to sign a Contributor's License Agreement. You can do so by going to https://cla.salesforce.com/sign-cla.

Build

To build the plugin locally, make sure to have yarn installed and run the following commands:

# Clone the repository
git clone [email protected]:salesforcecli/plugin-source

# Install the dependencies and compile
yarn install
yarn build

To use your plugin, run using the local ./bin/dev or ./bin/dev.cmd file.

# Run using local run file.
./bin/dev source:

There should be no differences when running via the Salesforce CLI or using the local run file. However, it can be useful to link the plugin to do some additional testing or run your commands from anywhere on your machine.

# Link your plugin to the sfdx cli
sfdx plugins:link .
# To verify
sfdx plugins

Usage

$ npm install -g @salesforce/plugin-source
$ sfdx COMMAND
running command...
$ sfdx (--version)
@salesforce/plugin-source/3.3.5 linux-x64 node-v18.20.2
$ sfdx --help [COMMAND]
USAGE
  $ sfdx COMMAND
...

Commands