[BUG][code-analyzer] PMD NullPointerException scanning two LWC JavaScript files
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- java, javascript
Direzione di ricerca
Start by running the documented sf code-analyzer run command with the AppExchange and Recommended:Security selectors against the workspace containing owJobDetail.js and owJobList.js. Investigate the PMD processing error and request a reduced reproduction because the source files are private. Done means both files are analyzed without a NullPointerException, or unsupported syntax produces a diagnostic identifying its location.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
Salesforce Code Analyzer's PMD engine throws a NullPointerException while scanning two Lightning Web Component JavaScript files, owJobDetail.js and owJobList.js. The scan produces an HTML report, but PMD does not complete analysis of those files.
The error occurred with Code Analyzer 5.13.0 and reproduced with 5.16.0 using the AppExchange and Recommended:Security rule selectors. I need a complete scan for a managed-package security review.
Output / Logs
PMD issued a processing error for owJobDetail.js:
NullPointerException: Cannot invoke "org.mozilla.javascript.ast.Name.visit(org.mozilla.javascript.ast.NodeVisitor)" because "this.varName" is null
PMD issued the same processing error for owJobList.js.
The run generated an HTML report with 15 violations (12 High, 3 Moderate), but PMD did not complete analysis of these two JavaScript files.
Steps To Reproduce
- From the root of a Salesforce project containing the two LWC JavaScript files, run:
sf code-analyzer run --rule-selector AppExchange --rule-selector Recommended:Security --workspace packages/ondaworx-job-board --output-file ../ow-job-board-security-review/CodeAnalyzerReport-v5.16.html
- Observe PMD processing errors for owJobDetail.js and owJobList.js.
- The same error occurred with plugin versions 5.13.0 and 5.16.0 on this Mac. The source is in a private managed-package repository, so I have not attached it publicly.
Expected Behavior
PMD should analyse both JavaScript files and either report rule violations or complete without a processing error. If the syntax is unsupported, it should provide a diagnostic that identifies the relevant syntax and location.
Operating System
macOS 26.5.2
Salesforce CLI Version
@salesforce/cli/2.141.6 darwin-x64 node-v22.22.3
Code Analyzer Plugin (code-analyzer) Version
code-analyzer 5.16.0
Node Version
v26.5.0
Java Version
openjdk version "21.0.12.1" 2026-08-18
Python Version
No response
Additional Context (Screenshots, Files, etc)
This scan is needed for a Salesforce managed-package security review. I have reproduced the error twice on this Mac with different plugin versions. I have not tested it on a second computer. I can provide further diagnostic information or a reduced reproduction if requested.
Workaround
No workaround found. Updating Code Analyzer from 5.13.0 to 5.16.0 did not resolve the error.
Urgency
High
- Lingua principale
- TypeScript
- Stelle
- 240
- Fork
- 52
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di forcedotcom/code-analyzer
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
forcedotcom/code-analyzer#2094 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
forcedotcom/code-analyzer#2093 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
forcedotcom/code-analyzer#2091 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
forcedotcom/code-analyzer#2090 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
forcedotcom/code-analyzer#2099 ·
Tutte le issue di forcedotcom/code-analyzer
Issue simili
-
bug via-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
pingdotgg/t3code#14452 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
solana-foundation/program-examples#747 · 1 commento ·
I maintainer di solito rispondono entro 9 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
remotion-dev/remotion#11847 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
openwatersio/slackwater#355 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
melgarafael/DeskcommCRM#1998 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno