@salesforce/cli 2.111.3 → 2.111.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.
Files changed (5) hide show
  1. package/README.md +97 -97
  2. package/npm-shrinkwrap.json +807 -1309
  3. package/oclif.lock +782 -1070
  4. package/oclif.manifest.json +35 -14
  5. package/package.json +21 -21
package/oclif.manifest.json CHANGED
@@ -12,9 +12,18 @@
12
12
  "Display all the default rule values for the recommended rules, instead of only the rule values you've explicitly overriden in your `code-analyzer.yml` file. By default, only overriden rule values are displayed unless you specify the `--include-unmodified-rules` flag:\n<%= config.bin %> <%= command.id %> --rule-selector Recommended --include-unmodified-rules",
13
13
  "Display the configuration state associated with all the rules that are applicable to the files targeted within the folder `./src`:\n<%= config.bin %> <%= command.id %> --target ./src",
14
14
  "Display any relevant configuration settings associated with the rule name 'no-undef' from the 'eslint' engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:no-undef",
15
+ "Display any relevant configuration settings associated with PMD rules whose severity is 2 or 3:\n<%= config.bin %> <%= command.id %> --rule-selector \"pmd:(2,3)\"",
15
16
  "Load an existing configuration file called `existing-config.yml`, and then write the configuration to a new file called `new-config.yml`, the configuration state that is applicable to all rules that are relevant to the workspace located in the current folder:\n<%= config.bin %> <%= command.id %> --config-file ./existing-config.yml --workspace . --output-file ./subfolder-config.yml"
16
17
  ],
17
18
  "flags": {
19
+ "flags-dir": {
20
+ "helpGroup": "GLOBAL",
21
+ "name": "flags-dir",
22
+ "summary": "Import flag values from a directory.",
23
+ "hasDynamicHelp": false,
24
+ "multiple": false,
25
+ "type": "option"
26
+ },
18
27
  "workspace": {
19
28
  "char": "w",
20
29
  "description": "Use the `--workspace` flag to display only the configuration associated with the rules that apply to the files that make up your workspace. Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders.\n\nThis command uses the types of files in the workspace, such as JavaScript or Typescript, to determine the applicable configuration state. For example, if your workspace contains only JavaScript files, then the command doesn't display configuration state associated with TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nSome engines can be configured to add additional rules based on what it finds in your workspace. For example, if you set the engines.eslint.auto_discover_eslint_config value of your `code-analyzer.yml` file to true, then supplying your workspace allows the \"eslint\" engine to examine your files in order to find ESLint configuration files that could potentially add in additional rules.\n\nIf you specify `--target` but not `--workspace`, then the current folder '.' is used as your workspace.",
@@ -37,13 +46,12 @@
37
46
  },
38
47
  "rule-selector": {
39
48
  "char": "r",
40
- "description": "Use the `--rule-selector` flag to display only the configuration associated with the rules based on specific criteria. You can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names.\n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection. For example, `--rule-selector eslint:Security` reduces the output to only contain the configuration state associated with the rules from the \"eslint\" engine that have the \"Security\" tag. To add multiple rule selectors together (a union), specify the `--rule-selector` flag multiple times, such as `--rule-selector eslint:Recommended --rule-selector retire-js:3`.\n\nIf you don't specify this flag, then the command uses the \"all\" rule selector.\n\nRun `<%= config.bin %> <%= command.id %> --rule-selector Recommended` to display the configuration state associated with just the 'Recommended' rules, instead of all the rules.",
49
+ "description": "Use the `--rule-selector` flag to display only the configuration associated with the rules based on specific criteria. You can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names.\n\nYou can further filter the list by combining different criteria using colons to represent logical AND, commas to represent logical OR, and parentheses to create groupings. For example, `--rule-selector \"pmd:(Performance,Security):2\"` reduces the output to only contain the configuration state associated with PMD rules that have the Performance or Security tag and a severity of 2. You may also specify the flag multiple times to OR multiple selectors together. For example, `--rule-selector Performance,Security` is equivalent to `--rule-selector Performance --rule-selector Security`. Note that if you use parentheses in your selector, the selector should be wrapped in double-quotes.\n\nIf you don't specify this flag, then the command uses the \"all\" rule selector.\n\nRun `<%= config.bin %> <%= command.id %> --rule-selector Recommended` to display the configuration state associated with just the 'Recommended' rules, instead of all the rules.",
41
50
  "name": "rule-selector",
42
- "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
51
+ "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons and commas, and grouped by parentheses.",
43
52
  "default": [
44
53
  "all"
45
54
  ],
46
- "delimiter": ",",
47
55
  "hasDynamicHelp": false,
48
56
  "multiple": true,
49
57
  "type": "option"
@@ -83,8 +91,7 @@
83
91
  "strict": true,
84
92
  "summary": "Output the current state of configuration for Code Analyzer.",
85
93
  "enableJsonFlag": false,
86
- "SF_ENV": "SF_ENV",
87
- "isESM": false,
94
+ "isESM": true,
88
95
  "relativePath": [
89
96
  "lib",
90
97
  "commands",
@@ -111,11 +118,20 @@
111
118
  "Get a more accurate list of the rules that apply specifically to your workspace (all the files in the current folder):\n<%= config.bin %> <%= command.id %> --rule-selector all --workspace .",
112
119
  "List the recommended rules associated with a workspace that targets all the files in the folder \"./other-source\" and only the Apex class files (extension .cls) under the folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector Recommended --workspace . --target ./other-source --target ./force-app/**/*.cls",
113
120
  "List all the \"eslint\" engine rules that have a moderate severity (3) and the recommended \"retire-js\" engine rules with any severity:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended",
121
+ "List all the \"pmd\" engine rules that have a severity of moderate (3) or high (2) and the \"Performance\" tag.\n<%= config.bin %> <%= command.id %> --rule-selector \"pmd:(2,3):Performance\"",
114
122
  "Similar to the previous example, but apply the rule overrides and engine settings from the configuration file called `code-analyzer2.yml` in the current folder. If, for example, you changed the severity of an \"eslint\" rule from moderate (3) to high (2) in the configuration file, then that rule isn't listed:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended --config-file ./code-analyzer2.yml",
115
123
  "List the details of the \"getter-return\" rule of the \"eslint\" engine and the rules named \"no-inner-declarations\" in any engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:getter-return --rule-selector no-inner-declarations --view detail",
116
124
  "List the details of the recommended \"eslint\" engine rules that have the tag \"problem\" and high severity level (2) that apply when targeting the files within the folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector eslint:Recommended:problem:2 --view detail --target ./force-app"
117
125
  ],
118
126
  "flags": {
127
+ "flags-dir": {
128
+ "helpGroup": "GLOBAL",
129
+ "name": "flags-dir",
130
+ "summary": "Import flag values from a directory.",
131
+ "hasDynamicHelp": false,
132
+ "multiple": false,
133
+ "type": "option"
134
+ },
119
135
  "workspace": {
120
136
  "char": "w",
121
137
  "description": "Use the `--workspace` flag to return a more accurate list of the rules that apply to the files that make up your workspace. Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders. \n\nThe command uses the types of files in the workspace, such as JavaScript or Typescript, to determine which rules to list. For example, if your workspace contains only JavaScript files, the command doesn't list TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nSome engines may be configured to add additional rules based on what it finds in your workspace. For example, if you set the engines.eslint.auto_discover_eslint_config value of your `code-analyzer.yml` file to true, then supplying your workspace allows the \"eslint\" engine to examine your files in order to find ESLint configuration files that could potentially add in additional rules.\n\nIf you specify `--target` but not `--workspace`, then the current folder '.' is used as your workspace.",
@@ -138,13 +154,12 @@
138
154
  },
139
155
  "rule-selector": {
140
156
  "char": "r",
141
- "description": "Use the `--rule-selector` flag to select the list of rules based on specific criteria. For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\". \n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection. For example, `--rule-selector eslint:Security` lists rules associated only with the \"eslint\" engine that have the Security tag. The flag `--rule-selector eslint:Security:3` flag lists the \"eslint\" rules that have the Security tag and moderate severity (3). To add multiple rule selectors together (a union), specify the `--rule-selector` flag multiple times, such as `--rule-selector eslint:Recommended --rule-selector retire-js:3`.\n\nRun `<%= config.bin %> <%= command.id %> --rule-selector all` to list the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
157
+ "description": "Use the `--rule-selector` flag to select the list of rules based on specific criteria. For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\". \n\nYou can further filter the list by combining different criteria using colons to represent logical AND, commas to represent logical OR, and parentheses to create groupings. For example, `--rule-selector \"pmd:(Performance,Security):2\"` lists rules associated only with the \"pmd\" engine that have the Security or Performance tags and a high severity (2). You may also specify the flag multiple times to OR multiple selectors together. For example, `--rule-selector Performance,Security` is equivalent to `--rule-selector Performance --rule-selector Security`. Note that if you use parentheses in your selector, the selector should be wrapped in double-quotes. \n\nRun `<%= config.bin %> <%= command.id %> --rule-selector all` to list the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
142
158
  "name": "rule-selector",
143
159
  "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
144
160
  "default": [
145
161
  "Recommended"
146
162
  ],
147
- "delimiter": ",",
148
163
  "hasDynamicHelp": false,
149
164
  "multiple": true,
150
165
  "type": "option"
@@ -191,8 +206,7 @@
191
206
  "strict": true,
192
207
  "summary": "List the rules that are available to analyze your code.",
193
208
  "enableJsonFlag": false,
194
- "SF_ENV": "SF_ENV",
195
- "isESM": false,
209
+ "isESM": true,
196
210
  "relativePath": [
197
211
  "lib",
198
212
  "commands",
@@ -216,12 +230,21 @@
216
230
  "Analyze the files using all the \"eslint\" rules:\n<%= config.bin %> <%= command.id %> --rule-selector eslint",
217
231
  "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:all",
218
232
  "Analyze the files using all rules for all engines:\n<%= config.bin %> <%= command.id %> --rule-selector all",
233
+ "Analyze the files using only rules in the \"pmd\" engine with a severity of high (2) or moderate (3), and the \"Performance\" tag.\n<%= config.bin %> <%= command.id %> --rule-selector \"pmd:(2,3):Performance\"",
219
234
  "Analyze files using the recommended \"retire-js\" rules; target all the files in the folder \"./other-source\" and only the Apex class files (extension .cls) in the folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector retire-js:Recommended --target ./other-source --target ./force-app/**/*.cls",
220
235
  "Specify a custom configuration file and output the results to the \"results.csv\" file in CSV format; the commands fails if it finds a violation that exceeds the moderate severity level (3):\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer2.yml --output-file results.csv --severity-threshold 3",
221
236
  "Analyze the files using all the \"eslint\" engine rules that have a moderate severity (3) and the recommended \"retire-js\" engine rules with any severity:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended",
222
237
  "Analyze the files using only the \"getter-return\" rule of the \"eslint\" engine and any rule named \"no-inner-declarations\" from any engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:getter-return --rule-selector no-inner-declarations"
223
238
  ],
224
239
  "flags": {
240
+ "flags-dir": {
241
+ "helpGroup": "GLOBAL",
242
+ "name": "flags-dir",
243
+ "summary": "Import flag values from a directory.",
244
+ "hasDynamicHelp": false,
245
+ "multiple": false,
246
+ "type": "option"
247
+ },
225
248
  "workspace": {
226
249
  "char": "w",
227
250
  "description": "Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders.\n\nSome engines often need your entire code base to perform an analysis, even if you want to target only a subset of the files within your workspace , such as with the `--target` flag. For example, the Salesforce Graph Engine might need to compile your entire project in order to properly build a graph so it can perform a data flow analysis on the paths that start in your targeted files.\n\nIf you don't specify the `--workspace` flag, then the current folder '.' is used as your workspace.",
@@ -247,13 +270,12 @@
247
270
  },
248
271
  "rule-selector": {
249
272
  "char": "r",
250
- "description": "Use the `--rule-selector` flag to select the list of rules to run based on specific criteria. For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\".\n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection. For example, `--rule-selector eslint:Security` runs rules associated only with the \"eslint\" engine that have the Security tag. The flag `--rule-selector eslint:Security:3` flag runs the \"eslint\" rules that have the Security tag and moderate severity (3). To add multiple rule selectors together (a union), specify the `--rule-selector` flag multiple times, such as `--rule-selector eslint:Recommended --rule-selector retire-js:3`.\n\nRun `<%= config.bin %> code-analyzer rules --rule-selector all` to see the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
273
+ "description": "Use the `--rule-selector` flag to select the list of rules to run based on specific criteria. For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\".\n\nYou can further filter the list by combining different criteria using colons to represent logical AND, commas to represent logical OR, and parentheses to create groupings. For example, `--rule-selector \"pmd:(Performance,Security):2\"` runs rules associated only with the \"pmd\" engine that have the Security or Performance tags and a high severity (2). You may also specify the flag multiple times to OR multiple selectors together. For example, `--rule-selector Performance,Security` is equivalent to `--rule-selector Performance --rule-selector Security`. Note that if you use parentheses in your selector, the selector should be wrapped in double-quotes.\n\nRun `<%= config.bin %> code-analyzer rules --rule-selector all` to see the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
251
274
  "name": "rule-selector",
252
275
  "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
253
276
  "default": [
254
277
  "Recommended"
255
278
  ],
256
- "delimiter": ",",
257
279
  "hasDynamicHelp": false,
258
280
  "multiple": true,
259
281
  "type": "option"
@@ -309,8 +331,7 @@
309
331
  "strict": true,
310
332
  "summary": "Analyze your code with a selection of rules to ensure good coding practices.",
311
333
  "enableJsonFlag": false,
312
- "SF_ENV": "SF_ENV",
313
- "isESM": false,
334
+ "isESM": true,
314
335
  "relativePath": [
315
336
  "lib",
316
337
  "commands",
@@ -4159,5 +4180,5 @@
4159
4180
  "requiresProject": true
4160
4181
  }
4161
4182
  },
4162
- "version": "2.111.3"
4183
+ "version": "2.111.5"
4163
4184
  }
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@salesforce/cli",
3
3
  "description": "The Salesforce CLI",
4
- "version": "2.111.3",
4
+ "version": "2.111.5",
5
5
  "author": "Salesforce",
6
6
  "bin": {
7
7
  "sf": "./bin/run.js",
@@ -76,13 +76,13 @@
76
76
  "@salesforce/plugin-user"
77
77
  ],
78
78
  "jitPlugins": {
79
- "@salesforce/plugin-code-analyzer": "5.5.0",
79
+ "@salesforce/plugin-code-analyzer": "5.6.0",
80
80
  "@salesforce/plugin-community": "3.3.44",
81
- "@salesforce/plugin-custom-metadata": "3.3.68",
81
+ "@salesforce/plugin-custom-metadata": "3.3.69",
82
82
  "@salesforce/plugin-dev": "2.5.1",
83
83
  "@salesforce/plugin-devops-center": "1.2.27",
84
84
  "@salesforce/plugin-flow": "1.0.2",
85
- "@salesforce/plugin-signups": "2.6.52",
85
+ "@salesforce/plugin-signups": "2.6.53",
86
86
  "@salesforce/sfdx-plugin-lwc-test": "1.2.1"
87
87
  },
88
88
  "devPlugins": [
@@ -144,35 +144,35 @@
144
144
  },
145
145
  "dependencies": {
146
146
  "@inquirer/select": "^2.3.5",
147
- "@oclif/core": "4.7.2",
148
- "@oclif/plugin-autocomplete": "3.2.37",
147
+ "@oclif/core": "4.8.0",
148
+ "@oclif/plugin-autocomplete": "3.2.38",
149
149
  "@oclif/plugin-commands": "4.1.37",
150
150
  "@oclif/plugin-help": "6.2.34",
151
151
  "@oclif/plugin-not-found": "3.2.71",
152
152
  "@oclif/plugin-plugins": "5.4.51",
153
- "@oclif/plugin-search": "1.2.33",
154
- "@oclif/plugin-update": "4.7.11",
153
+ "@oclif/plugin-search": "1.2.34",
154
+ "@oclif/plugin-update": "4.7.13",
155
155
  "@oclif/plugin-version": "2.2.35",
156
- "@oclif/plugin-warn-if-update-available": "3.1.50",
157
- "@oclif/plugin-which": "3.2.41",
156
+ "@oclif/plugin-warn-if-update-available": "3.1.51",
157
+ "@oclif/plugin-which": "3.2.42",
158
158
  "@salesforce/core": "^8.9.1",
159
159
  "@salesforce/kit": "^3.1.6",
160
- "@salesforce/plugin-agent": "1.24.18",
161
- "@salesforce/plugin-apex": "3.8.3",
160
+ "@salesforce/plugin-agent": "1.24.21",
161
+ "@salesforce/plugin-apex": "3.8.5",
162
162
  "@salesforce/plugin-api": "1.3.3",
163
- "@salesforce/plugin-auth": "3.9.14",
163
+ "@salesforce/plugin-auth": "3.9.17",
164
164
  "@salesforce/plugin-data": "4.0.59",
165
165
  "@salesforce/plugin-deploy-retrieve": "3.23.12",
166
- "@salesforce/plugin-info": "3.4.93",
167
- "@salesforce/plugin-limits": "3.3.67",
166
+ "@salesforce/plugin-info": "3.4.95",
167
+ "@salesforce/plugin-limits": "3.3.70",
168
168
  "@salesforce/plugin-marketplace": "1.3.8",
169
- "@salesforce/plugin-org": "5.9.38",
170
- "@salesforce/plugin-packaging": "2.22.2",
171
- "@salesforce/plugin-schema": "3.3.82",
169
+ "@salesforce/plugin-org": "5.9.41",
170
+ "@salesforce/plugin-packaging": "2.22.4",
171
+ "@salesforce/plugin-schema": "3.3.86",
172
172
  "@salesforce/plugin-settings": "2.4.50",
173
- "@salesforce/plugin-sobject": "1.4.76",
173
+ "@salesforce/plugin-sobject": "1.4.77",
174
174
  "@salesforce/plugin-telemetry": "3.6.62",
175
- "@salesforce/plugin-templates": "56.3.66",
175
+ "@salesforce/plugin-templates": "56.3.69",
176
176
  "@salesforce/plugin-trust": "3.7.113",
177
177
  "@salesforce/plugin-user": "3.6.38",
178
178
  "@salesforce/sf-plugins-core": "12.2.5",
@@ -262,7 +262,7 @@
262
262
  "@salesforce/ts-sinon": "^1.4.31",
263
263
  "@salesforce/ts-types": "^2.0.11",
264
264
  "aws-sdk": "^2.1692.0",
265
- "oclif": "^4.22.32",
265
+ "oclif": "^4.22.38",
266
266
  "ts-node": "^10.9.2",
267
267
  "typescript": "^5.9.3"
268
268
  },