[BUG][vscode-extension] Silent crash when analyzing LWC with LWC Base Config disabled

[fabiobarcelona]

Have you tried to resolve this issue yourself first?

• I confirm I have gone through the above steps and still have an issue to report.

Bug Description

When analyzing LWCs with decorators with the disable_lwc_base_config set to true, the extension shows success analyzing 0 files, and doesn't report any eslint error, even though the analyzed file has several.

Using the Output tab in VS Code shows no error (quick fix here: logs shows code-analyzer version as 5.9.0, whereas I'm using v5.10.0):

Using the CLI Command returns the actual error:

> sf code-analyzer run --rule-selector AppExchange --rule-selector cpd --rule-selector eslint --target "**/lwc/**/*.js" --target "**/lwc/**/*.html" --target "**/lwc/**/*.css" --config-file ./config/code-analyzer.yml --output-file reports/sfca-results-lwc.html --view detail && npm run analyze:open:lwc
-----
 »   Error: Engine 'eslint' [23:1:12.242]:
 »       When scanning file 'pathToLwcJsFile' with the eslint engine, ESLint gave the following error:
 »           Parsing error: Unexpected character '@'

The LWC I'm analyzing uses an @api decorator, which is likely causing the error.

Output / Logs

Steps To Reproduce

1. Set disable_lwc_base_config to true in code-analyzer config
2. Analyze any LWC that uses decorators with the VS Code Extension and the ESLint engine

Expected Behavior

Either return the error as a VS Code toast notification, allow non-LWC rules only to be used with LWCs too, or notify the user that disabling the LWC Base Config is not possible when analyzing LWCs.

Operating System

Windows 11 Pro 25H2

Visual Studio Code Version

1.109.5

Extension Version

1.16.0

Salesforce CLI Version

@salesforce/cli/2.124.7 win32-x64 node-v22.17.1

Code Analyzer CLI Plugin Version

code-analyzer 5.10.0

Node Version

v22.17.1

Java Version

java 21.0.8 2025-07-15 LTS

Python Version

Python 3.14.3

Additional Context (Screenshots, Files, etc)

No response

Workaround

No response

Urgency

Low

[aruntyagiTutu]

Yes @fabiobarcelona, I am able to reproduce this behavior with disable_lwc_base_config set to true. This is not specific to the latest version and is consistent with previous versions as well. Please allow me some time to get back to you with more details.

[aruntyagiTutu]

meanwhile can you please run sf plugins and share the output ?

[aruntyagiTutu]

version number is coming from VS code cache,

needs to reload the VS Code window to clear the cache:

• Command Palette (Cmd/Ctrl + Shift + P) → "Developer: Reload Window"
• Or restart VS Code entirely

[fabiobarcelona]

meanwhile can you please run sf plugins and share the output ?

Sure, here it is:

PS D:\Salesforce\Projects\sfdx-project> sf plugins
code-analyzer 5.10.0
sfdx-plugin-source-read 1.5.6

Uninstalled JIT Plugins:
community 3.3.48
custom-metadata 3.3.76
dev 2.5.1
devops-center 1.2.27
flow 1.0.5
signups 2.6.56
@salesforce/sfdx-plugin-lwc-test 1.2.1

version number is coming from VS code cache,

needs to reload the VS Code window to clear the cache:

• Command Palette (Cmd/Ctrl + Shift + P) → "Developer: Reload Window"
• Or restart VS Code entirely

You're right, now it says 5.10.0, thanks.

[git2gus]

This issue has been linked to a new work item: W-21462741

[aruntyagiTutu]

Hi @fabiobarcelona

We have released Code Analyzer v5.10.1, which fixes the decorator parsing issue you reported.

To test the fix:

1. Update to the latest version:
   sf plugins install @salesforce/plugin-code-analyzer@latest
2. Run your analysis again with disable_lwc_base_config: true in your configuration.

The issue where LWC files containing decorators (@api, @track, @wire) failed to parse should now be resolved.
Please let us know if you encounter any issues with the new version.

Thanks again for reporting this