Changing components not showing up in app
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- typescript
- Área
- devtools
Línea de trabajo
Start by reproducing the issue with the sf lightning dev app --device-type desktop -n Sales command and the Hello World LWC component. Trace the update reported for helloWorld.js in the local development server logs, then verify that changing "World" to "Sunshine" appears in the live preview.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Changing a LWC component is not creating visible changes.
Steps To Reproduce:
- Create the Hello World LWC Component, and follow all the steps.
- Confirm the component is on the Sales page.
- Start the local development server:
SF_LOG_LEVEL=30 sf lightning dev app --device-type desktop -n Sales - Edit
helloWorld.jsto change "World" to "Sunshine" - Confirm from the logs that the plugin has noticed the change:
tail -f ~/.sf/sf-2025-03-13.log
{"level":30,"time":1741886202203,"name":"sf:AuthInfo","msg":"Returning fields for a connection using OAuth config."}
{"level":30,"time":1741886202599,"name":"sf:core:config","msg":"Key local-web-server-identity-data already exists in allowedProperties, skipping."}
{"level":30,"time":1741886202599,"name":"sf:core:config","msg":"Key local-dev-server-certificate-data already exists in allowedProperties, skipping."}
{"level":30,"time":1741886202599,"name":"sf:core:config","msg":"Key local-dev-server-port already exists in allowedProperties, skipping."}
{"level":30,"time":1741886202599,"name":"sf:core:config","msg":"Key local-dev-server-workspace already exists in allowedProperties, skipping."}
{"level":30,"time":1741886202747,"name":"sf:LightningDevApp","msg":"[LWC Dev Server] LWC Dev Server started at port:8081"}
{"level":30,"time":1741886202846,"name":"sf:oclif:AuthInfo","msg":"Returning fields for a connection using OAuth config."}
{"level":30,"time":1741886202850,"name":"sf:oclif:AuthInfo","msg":"Returning fields for a connection using OAuth config."}
{"level":30,"time":1741886202859,"name":"sf:oclif:AuthInfo","msg":"Returning fields for a connection using OAuth config."}
{"level":30,"time":1741886202862,"name":"sf:oclif:AuthInfo","msg":"Returning fields for a connection using OAuth config."}
{"level":30,"time":1741886263857,"name":"sf:LightningDevApp","msg":"[LWC Dev Server] File 'helloWorld.js' modified - updating."}
- Go to the live update website and see that the component still says "Hello World" not "Hello Sunshine".
Expected Result
In the live preview, it should have changed the value to "Hello Sunshine"
Actual Result
There was not change to the LWC.
Additional Information
System Information
SF CLI:
shell: zsh
{
"architecture": "darwin-arm64",
"cliVersion": "@salesforce/cli/2.78.3",
"nodeVersion": "node-v22.13.0",
"osVersion": "Darwin 24.3.0",
"rootPath": "/usr/local/lib/sf",
"shell": "zsh",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.21 (core)",
"@oclif/plugin-commands 4.1.20 (core)",
"@oclif/plugin-help 6.2.25 (core)",
"@oclif/plugin-not-found 3.2.40 (core)",
"@oclif/plugin-plugins 5.4.32 (core)",
"@oclif/plugin-search 1.2.21 (core)",
"@oclif/plugin-update 4.6.31 (core)",
"@oclif/plugin-version 2.2.23 (core)",
"@oclif/plugin-warn-if-update-available 3.1.33 (core)",
"@oclif/plugin-which 3.2.29 (core)",
"@salesforce/cli 2.78.3 (core)",
"apex 3.6.8 (core)",
"api 1.3.3 (core)",
"auth 3.6.94 (core)",
"data 4.0.11 (core)",
"deploy-retrieve 3.20.0 (core)",
"info 3.4.39 (core)",
"lightning-dev 2.10.3 (user) published 9 days ago (Mon Mar 03 2025)",
"limits 3.3.46 (core)",
"marketplace 1.3.7 (core)",
"org 5.2.32 (core)",
"packaging 2.9.17 (core)",
"schema 3.3.50 (core)",
"settings 2.4.16 (core)",
"sobject 1.4.50 (core)",
"telemetry 3.6.33 (core)",
"templates 56.3.38 (core)",
"trust 3.7.65 (core)",
"user 3.6.9 (core)"
]
}
OS: Mac OS, M1
- Lenguaje dominante
- TypeScript
- Estrellas
- 19
- Forks
- 19
- Merge medio
- 3 d 12 h
- PR fusionados (30 d)
- 2
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de salesforcecli/plugin-lightning-dev
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
salesforcecli/plugin-lightning-dev#686 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
salesforcecli/plugin-lightning-dev#627 · 2 comentarios · 1 reacción ·
-
BUG P2
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
salesforcecli/plugin-lightning-dev#544 · 4 comentarios ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
salesforcecli/plugin-lightning-dev#456 · 1 reacción ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Todos los issues de salesforcecli/plugin-lightning-dev
Issues similares
-
comp/desktop P3 type/bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
NousResearch/hermes-agent#118866 ·
-
Browser Waiting for: Product Owner
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
getsentry/sentry-javascript#24577 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
agilepathway/label-checker#640 ·
-
Plugin stuck at "loading" on DSH 0.1.6-alpha.2 — turnTail list slot registration missing options.id Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Add 2021 Cup data to website Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
chrisparsons83/flexspotff#153 ·