Changing components not showing up in app
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- devtools
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 19
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from salesforcecli/plugin-lightning-dev
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
salesforcecli/plugin-lightning-dev#686 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
salesforcecli/plugin-lightning-dev#627 · 2 comments · 1 reaction ·
-
BUG P2
Difficulty 3/5 1-2 days Newbie friendliness 45/100
salesforcecli/plugin-lightning-dev#544 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
salesforcecli/plugin-lightning-dev#456 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in salesforcecli/plugin-lightning-dev
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·