@salesforce/cli 2.82.5 → 2.82.6

package/README.md

@@ -7,6 +7,7 @@
 
 # Getting Started
 
+- [Release notes](https://github.com/forcedotcom/cli/tree/main/releasenotes)
 - Read the [sf Plugin Developer Guide](https://github.com/salesforcecli/cli/wiki/Quick-Introduction-to-Developing-sf-Plugins) to learn how to develop a `sf` plugin.
 - Are you migrating an `sfdx` plugin to `sf`? Then check out the [migration section](https://github.com/salesforcecli/cli/wiki/Migrate-Plugins-Built-for-sfdx) of the developer guide.
 - Read [this section of the Setup Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_move_to_sf_v2.htm) for easy instructions on how to move from your `sfdx` (v7) installation to `sf` (v2).
@@ -24,7 +25,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (--version|-v)
-@salesforce/cli/2.82.5 linux-x64 node-v22.14.0
+@salesforce/cli/2.82.6 linux-x64 node-v22.14.0
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND

package/dist/hooks/preparse.js

@@ -70,7 +70,8 @@ const hook = async function ({ argv, options, context }) {
         if (contents === undefined) {
             return [name, undefined];
         }
-        const values = ext === '.json' ? [JSON.stringify(JSON.parse(contents))] : contents?.trim().split('\n');
+        const crlf = contents.search('\r\n') !== -1;
+        const values = ext === '.json' ? [JSON.stringify(JSON.parse(contents))] : contents?.trim().split(crlf ? '\r\n' : '\n');
         return [name, values];
     }));
     const newArgv = [...argv];

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@salesforce/cli",
-  "version": "2.82.5",
+  "version": "2.82.6",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@salesforce/cli",
-      "version": "2.82.5",
+      "version": "2.82.6",
       "hasInstallScript": true,
       "license": "BSD-3-Clause",
       "dependencies": {

package/oclif.manifest.json

@@ -5,13 +5,13 @@
       "args": {},
       "description": "Code Analyzer gives you the ability to configure settings that modify Code Analyzer's behavior, to override the tags and severity levels of rules, and to configure the engine specific settings.  Use this command to see the current state of this configuration. You can also save this state to a YAML-formatted file that you can modify for your needs.\n\nTo apply a custom configuration with Code Analyzer, either keep your custom configuration settings in a `code-analyzer.yml` file located in the current folder from which you are executing commands, or specify the location of your custom configuration file to the Code Analyzer commands with the --config-file flag.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.",
       "examples": [
-        "Display the current state of the Code Analyzer configuration using the default behavior: display top level configuration, display the engine and rule override settings associated with all the rules that have a \"Recommended\" tag; and automatically apply any existing custom configuration settings found in a `code-analyzer.yml` or `code-analyzer.yaml` file in the current folder:\n<%= config.bin %> <%= command.id %>",
-        "This example is identical to the previous one, assuming that `./code-analyzer.yml` exists in your current folder.\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer.yml --rule-selector Recommended",
+        "Display the current state of the Code Analyzer configuration using the default behavior: display top level configuration, display the engine and rule override settings associated with all the rules; and automatically apply any existing custom configuration settings found in a `code-analyzer.yml` or `code-analyzer.yaml` file in the current folder:\n<%= config.bin %> <%= command.id %>",
+        "This example is identical to the previous one, assuming that `./code-analyzer.yml` exists in your current folder.\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer.yml --rule-selector all",
         "Write the current state of configuration to the file `code-analyzer.yml`, including any configuration from an existing `code-analyzer.yml` file. The command preserves all values from the original config, but overwrites any comments:\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer.yml --output-file code-analyzer.yml",
-        "Display the configuration state for all rules, instead of just the recommended ones:\n<%= config.bin %> <%= command.id %> --rule-selector all",
-        "Display the configuration state associated with recommended rules that are applicable to your workspace folder, `./src`:\n<%= config.bin %> <%= command.id %> --workspace ./src",
-        "Display any relevant configuration settings associated with the rule name 'no-undef' from the 'eslint' engine:\n<%= config.bin %> <%= command.id %> --rule-selection eslint:no-undef",
-        "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 --rule-selection all --workspace . --output-file ./subfolder-config.yml"
+        "Display the configuration state for just the recommended rules, instead of all the rules:\n<%= config.bin %> <%= command.id %> --rule-selector Recommended",
+        "Display the configuration state associated with all the rules that are applicable to your workspace folder, `./src`:\n<%= config.bin %> <%= command.id %> --workspace ./src",
+        "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",
+        "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"
       ],
       "flags": {
         "workspace": {
@@ -26,11 +26,11 @@
         },
         "rule-selector": {
           "char": "r",
-          "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 \"Recommended\" tag rule selector.\n\nRun `<%= config.bin %> <%= command.id %>  --rule-selector all` to display the configuration state associated with all possible rules available, and not just the recommended ones.",
+          "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.",
           "name": "rule-selector",
           "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
           "default": [
-            "Recommended"
+            "all"
           ],
           "delimiter": ",",
           "hasDynamicHelp": false,
@@ -90,7 +90,7 @@
         "List the recommended rules for the \"eslint\" engine:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint:Recommended",
         "List all the rules for the \"eslint\" engine:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint",
         "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint:all",
-        "List all rules for all engines:\n<%= config.bin %> <%= command.id %>  --rule-selector all",
+        "List the details about all rules for all engines; also write the rules in JSON format to a file called \"rules.json\" in the \"out\" folder, which must already exist:\n<%= config.bin %> <%= command.id %>  --rule-selector all --output-file ./out/rules.json --view detail",
         "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 .",
         "List the recommended rules associated with a workspace that includes 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 ./other-source --workspace ./force-app/**/*.cls",
         "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",
@@ -131,12 +131,20 @@
           "multiple": false,
           "type": "option"
         },
+        "output-file": {
+          "char": "f",
+          "description": "If you specify a folder, such as \"--output-file ./out/rules.json\", the folder must already exist or you get an error. If the file already exists, it's overwritten without prompting.\n\nIf you don't specify this flag, the command outputs the rules to only the terminal.",
+          "name": "output-file",
+          "summary": "Name of the file where the selected rules are written. The file format depends on the extension you specify; currently, only .json is supported for JSON-formatted output.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
         "view": {
           "char": "v",
-          "description": "The format `table` is concise and shows minimal output, the format `detail` shows all available information.",
+          "description": "The format `table` is concise and shows minimal output, the format `detail` shows all available information. \n\nIf you specify neither --view nor --output-file, then the default table view is shown. If you specify --output-file but not --view, only summary information is shown in the terminal.",
           "name": "view",
           "summary": "Format to display the rules in the terminal.",
-          "default": "table",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
@@ -248,9 +256,9 @@
         },
         "output-file": {
           "char": "f",
-          "description": "If you don't specify this flag, the command outputs the results in the terminal. Use this flag to print the results to a file; the format of the results depends on the extension you provide. For example, \"--output-file results.csv\" creates a comma-separated values file. You can specify one of these extensions:\n\n- .csv\n- .html or .htm\n- .json\n- .sarif or .sarif.json\n- .xml\n\nTo output the results to multiple files, specify this flag multiple times.  For example: \"--output-file ./out/results.json --output-file ./out/report.html\" creates a JSON results file and an HTML file in the \"./out\" folder.",
+          "description": "If you don't specify this flag, the command outputs the results to only the terminal. Use this flag to print the results to a file; the format of the results depends on the extension you provide. For example, \"--output-file results.csv\" creates a comma-separated values file. You can specify one of these extensions:\n\n- .csv\n- .html or .htm\n- .json\n- .sarif or .sarif.json\n- .xml\n\nTo output the results to multiple files, specify this flag multiple times.  For example: \"--output-file results.json --output-file report.html\" creates both a JSON results file and an HTML file.\n\nIf you specify a folder, such as \"--output-file ./out/results.json\", the folder must already exist or you get an error. If the file already exists, it's overwritten without prompting.",
           "name": "output-file",
-          "summary": "Output file that contains the analysis results. The file format depends on the extension you specify, such as .csv, .html, .xml, and so on.",
+          "summary": "Name of the file where the analysis results are written. The file format depends on the extension you specify, such as .csv, .html, .xml, and so on.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -4403,5 +4411,5 @@
       ]
     }
   },
-  "version": "2.82.5"
+  "version": "2.82.6"
 }

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "2.82.5",
+  "version": "2.82.6",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run.js",
     "sfdx": "./bin/run.js"
   },
-  "homepage": "https://github.com/salesforcecli/cli",
+  "homepage": "https://github.com/forcedotcom/cli",
   "bugs": "https://github.com/forcedotcom/cli/issues",
   "engines": {
     "node": ">=18.6.0"
@@ -75,14 +75,14 @@
       "@salesforce/plugin-user"
     ],
     "jitPlugins": {
-      "@salesforce/plugin-code-analyzer": "5.0.0-beta.2",
+      "@salesforce/plugin-code-analyzer": "5.0.0-beta.3",
       "@salesforce/plugin-custom-metadata": "3.3.47",
       "@salesforce/plugin-community": "3.3.17",
       "@salesforce/plugin-dev": "2.5.1",
       "@salesforce/plugin-devops-center": "1.2.27",
       "@salesforce/plugin-signups": "2.6.19",
       "@salesforce/sfdx-plugin-lwc-test": "1.2.1",
-      "@salesforce/sfdx-scanner": "4.10.0"
+      "@salesforce/sfdx-scanner": "4.11.0"
     },
     "devPlugins": [
       "@oclif/plugin-command-snapshot",