@salesforce/plugin-telemetry 4.2.3 → 4.2.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -13,7 +13,7 @@ All command usage is recorded by initializing on the `init` oclif hook, recordin
13
13
  To debug the telemetry spawned process, run a command with the environment variables `SF_TELEMETRY_DEBUG=true` and `DEBUG=sf:telemetry`.
14
14
 
15
15
  ```bash
16
- SF_TELEMETRY_DEBUG=true DEBUG=sf:telemetry* ./bin/dev telemetry
16
+ SF_TELEMETRY_DEBUG=true DEBUG=sf:telemetry* ./bin/dev.js telemetry
17
17
  ```
18
18
 
19
19
  ## Getting Started
@@ -25,22 +25,21 @@ To build the plugin locally, make sure to have yarn installed and run the follow
25
25
  git clone git@github.com:salesforcecli/plugin-telemetry
26
26
 
27
27
  # Install the dependencies and compile
28
- yarn install
29
- yarn build
28
+ yarn && yarn build
30
29
  ```
31
30
 
32
- To use your plugin, run using the local `./bin/dev` or `./bin/dev.cmd` file.
31
+ To use your plugin, run using the local `./bin/dev.js` or `./bin/dev.cmd` file.
33
32
 
34
33
  ```bash
35
34
  # Run using local run file.
36
- ./bin/dev telemetry
35
+ ./bin/dev.js telemetry
37
36
  ```
38
37
 
39
38
  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.
40
39
 
41
40
  ```bash
42
- # Link your plugin to the sfdx cli
43
- sf plugins:link .
41
+ # Link your plugin to the sf cli
42
+ sf plugins link .
44
43
  # To verify
45
44
  sf plugins
46
45
  ```
@@ -41,5 +41,5 @@
41
41
  ]
42
42
  }
43
43
  },
44
- "version": "4.2.3"
44
+ "version": "4.2.5"
45
45
  }
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@salesforce/plugin-telemetry",
3
3
  "description": "Command usage and error telemetry for the Salesforce CLI",
4
- "version": "4.2.3",
4
+ "version": "4.2.5",
5
5
  "author": "Salesforce",
6
6
  "bugs": "https://github.com/forcedotcom/cli/issues",
7
7
  "enableO11y": true,
@@ -19,16 +19,16 @@
19
19
  "@oclif/plugin-command-snapshot": "^6.0.0",
20
20
  "@oclif/plugin-help": "^7.0.0",
21
21
  "@salesforce/cli-plugins-testkit": "^5.3.58",
22
- "@salesforce/dev-scripts": "^15.0.0",
23
- "@salesforce/plugin-command-reference": "^3.1.81",
22
+ "@salesforce/dev-scripts": "^15.0.1",
23
+ "@salesforce/plugin-command-reference": "^3.1.142",
24
24
  "@salesforce/ts-sinon": "^1.4.36",
25
25
  "@types/chai": "^4.3.17",
26
26
  "@types/debug": "^4.1.13",
27
27
  "@types/mocha": "^10.0.10",
28
28
  "@types/node": "^18",
29
29
  "@types/sinon": "^10.0.20",
30
- "eslint": "^10.4.0",
31
- "eslint-config-salesforce-typescript": "^7.0.0",
30
+ "eslint": "^10.14.0",
31
+ "eslint-config-salesforce-typescript": "^7.0.1",
32
32
  "oclif": "^5.0.0",
33
33
  "ts-node": "^10.9.2",
34
34
  "typescript": "^6.0.0"
@@ -209,7 +209,7 @@
209
209
  "exports": "./lib/index.js",
210
210
  "type": "module",
211
211
  "sfdx": {
212
- "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-telemetry/4.2.3.crt",
213
- "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-telemetry/4.2.3.sig"
212
+ "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-telemetry/4.2.5.crt",
213
+ "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-telemetry/4.2.5.sig"
214
214
  }
215
215
  }