open-index/open-npm huggingface dataset:
npm package: @salesforce/plugin-analytics
Description: Command usage and error analytics for the Salesforce CLI
Author: Salesforce
Latest version: 1.12.1
Deprecated: This package has been deprecated in favor of https://www.npmjs.com/package/@salesforce/plugin-telemetry

# @salesforce/plugin-analytics [DEPRECATED]

**As of 1/25/2021 this package has been deprecated in favor of the new [telemetry plugin](https://www.npmjs.com/package/@salesforce/plugin-telemetry). Please use that plugin instead.**

Logs command execution and error information to app insights using `@salesforce/telemetry`. All logs are recorded to a local file in the CLI cache directory. Before the CLI process exists, a new process will be spawned up to read the local file and send logs to app insights. This saves ~1-3 seconds of time it can take to spin up and tear down the telemetry services.

During the CLI process, other plugins and CLI code also record custom events to the local file to be sent in the spawned process. To do so, simply instantiate the Analytics class.

```
const analytics = await Analytics.create({});
analytics.record({
  eventName: 'SOME_EVENT_NAME',
  ...
});
```

To not output the acknowledgement warning, set `SFDX_TELEMETRY_DISABLE_ACKNOWLEDGEMENT` to true.

```
export SFDX_TELEMETRY_DISABLE_ACKNOWLEDGEMENT=true
```

## Development

To set up the project, just run `yarn && yarn test`.

To debug the project, it is helpful to link it in the CLI.

```
# In sfdx-plugin-analytics
yarn link

# In sfdx-cli
yarn link @salesforce/plugin-analytics
DEBUG=sfdx:analytics ./bin/run force
```

To debug the spawned process, set the telemetry in debug mode.

```
SFDX_TELEMETRY_DEBUG=true DEBUG=sfdx:analytics ./bin/run
```
npm package: @salesforce/plugin-deploy-retrieve-utils
Description: Utils for writing deploy and retrieve plugins
Latest version: 0.0.10
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

[![NPM](https://img.shields.io/npm/v/@salesforce/plugin-deploy-retrieve-utils.svg)](https://www.npmjs.com/package/@salesforce/plugin-deploy-retrieve-utils)

# Description

Utilities for writing plugins that deploy or retrieve metadata from Salesforce Orgs
npm package: @salesforce/plugin-generator
Description: Create your own sfdx plugin
Author: Salesforce
Latest version: 2.0.17
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Description

## **=== WARNING === This plugin has been deprecated and is no longer supported. Please use the [salesforcecli/plugin-dev](https://github.com/salesforcecli/plugin-dev) plugin instead.**

This is the generator plugin for building plugins for the Salesforce CLI. The generated sfdx plugin and command are built on top of the [oclif cli framework](https://github.com/oclif/oclif). A plug-in adds functionality to Salesforce CLI. Some plug-ins are provided by Salesforce and are installed by default when you install the CLI. Some plug-ins, built by Salesforce and others, you install. When you have a requirement that an existing plug-in doesn’t meet, you can build your own using Node.js.

**Note:** As of @salesforce/command@1.3.0, if you want to override the static usage property you must use a getter. For consistency, we recommend keeping the standard behavior rather than overriding the usage property.

# Usage

## Check Your Salesforce CLI Version

Starting with Salesforce CLI version 6.8.2, the plug-in generator is offered as a core plugin and can be used out of the box. To check your Salesforce CLI version:

```
$ sfdx --version
sfdx-cli/6.42.0-ae478b3cb8 (darwin-x64) node-v8.9.4
```

## Generate a Salesforce CLI Plugin

Follow the **[Salesforce CLI Plug-In Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_plugins.meta/sfdx_cli_plugins/cli_plugins.htm) **to create and update your plug-in. In the guide you will discover how to develop your own plug-ins for Salesforce CLI. Explore the Salesforce CLI architecture. Learn how to generate a plug-in using Salesforce Plug-In Generator, how to use Salesforce’s libraries to add functionality to your plug-in, and how to debug issues. Learn about our suggested style guidelines for naming and messages, and about our recommended best practices for plug-ins. And, peruse useful resources.

# Related Docs and Repositories

- [@forcedotcom/cli-packages](https://github.com/forcedotcom/cli-packages) - Lerna repository containing Salesforce CLI command api.
- [@forcedotcom/sfdx-core](https://github.com/forcedotcom/sfdx-core) - API for working with a Salesforce DX project and managing Salesforce orgs
- [@oclif/command](https://github.com/oclif/command) - Base command for oclif; this can be used directly without the generator
- [@oclif/config](https://github.com/oclif/config) - Most of the core setup for oclif lives here
- [@oclif/errors](https://github.com/oclif/errors) - Renders and logs errors from commands
- [@oclif/cli-ux](https://github.com/oclif/cli-ux) - Library for common CLI UI utilities
- [@oclif/test](https://github.com/oclif/test) - Test helper for oclif
npm package: @salesforce/plugin-login
Description: Login and logout commands for sf
Author: Salesforce
Latest version: 2.0.10

# plugin-login

[![NPM](https://img.shields.io/npm/v/@salesforce/plugin-login.svg?label=@salesforce/plugin-login)](https://www.npmjs.com/package/@salesforce/plugin-login) [![Downloads/week](https://img.shields.io/npm/dw/@salesforce/plugin-login.svg)](https://npmjs.org/package/@salesforce/plugin-login) [![License](https://img.shields.io/badge/License-BSD%203--Clause-brightgreen.svg)](https://raw.githubusercontent.com/salesforcecli/plugin-login/main/LICENSE.txt)

## Install

```bash
sf plugins:install plugin-login@x.y.z
```

## Issues

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

## Contributing

1. Please read our [Code of Conduct](CODE_OF_CONDUCT.md)
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](#build)
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](#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:

```bash
# Clone the repository
git clone git@github.com:salesforcecli/plugin-login

# Install the dependencies and compile
yarn install
yarn build
```

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

```bash
# Run using local run file.
./bin/dev login
```

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.

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

## Commands

<!-- commands -->

<!-- commandsstop -->