command "lightning dev app" not working, throwing error "missing message messages:flags.optionalTargetOrg.summary"
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 25/100
- Type d'issue
- Bug
- Clarté
- À clarifier
- Activité
- À l'abandon
- Stack technique
- typescript
Piste de recherche
Start by reproducing the reported failures with sf lightning dev app and sf lightning dev site -n demo on Windows, using the listed CLI and plugin versions. Inspect the plugin command entry points and .localdev/demo/app/site/.metadata/runtime-info.json; completion should address the missing message, initial folder error, and documented LWC refresh behavior without introducing regressions.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Summary
command "lightning dev app" not working, throwing error "missing message messages:flags.optionalTargetOrg.summary for locale en_US"
Details:
When I'm running sf lightning dev app command, it is asking for the device type and the app, but failed after that
The same error I got when I installed the plugin with command
sf plugins install @salesforce/plugin-lightning-dev
I used powershell and ran that with admin permissions.
Not sure if the following point is related to any issue mentioned above, but here are the details.
When I run the site with sf lightning dev site -n demo, this opens the preview in browser, but no further changes in lwc are reflected there, tried simple text changes to adding more tags, page refresh doesn't help as well.
Also, when I run the site command first time, I get the following error even if I run it as admin, though it started working when I manually renamed the folder from bld to app.
Expected Result
- Plugin should be installed without any error
- lightning dev app command should work fine
- output window for
lightning dev site commandshould be refreshed automatically on lwc changes as mentioned in documentation
Actual Result
- Plugin installation should be succeeded without any error
- lightning dev app command fails with the error
- lightning dev site command should refresh the output automatically
System Information
SF CLI: powershell
sf version output
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.83.7",
"nodeVersion": "node-v22.14.0",
"osVersion": "Windows_NT 10.0.22631",
"rootPath": "C:\\Program Files\\sf\\client",
"shell": "powershell",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.26 (core)",
"@oclif/plugin-commands 4.1.22 (core)",
"@oclif/plugin-help 6.2.27 (core)",
"@oclif/plugin-not-found 3.2.48 (core)",
"@oclif/plugin-plugins 5.4.36 (core)",
"@oclif/plugin-search 1.2.23 (core)",
"@oclif/plugin-update 4.6.36 (core)",
"@oclif/plugin-version 2.2.27 (core)",
"@oclif/plugin-warn-if-update-available 3.1.38 (core)",
"@oclif/plugin-which 3.2.34 (core)",
"@salesforce/cli 2.83.7 (core)",
"apex 3.6.11 (core)",
"api 1.3.3 (core)",
"auth 3.6.108 (core)",
"data 4.0.24 (core)",
"deploy-retrieve 3.21.3 (core)",
"info 3.4.51 (core)",
"lightning-dev 2.10.3 (user) published 38 days ago (Tue Mar 04 2025)",
"limits 3.3.51 (core)",
"marketplace 1.3.7 (core)",
"org 5.5.7 (core)",
"packaging 2.12.3 (core)",
"schema 3.3.58 (core)",
"settings 2.4.22 (core)",
"sobject 1.4.53 (core)",
"telemetry 3.6.37 (core)",
"templates 56.3.43 (core)",
"trust 3.7.78 (core)",
"user 3.6.16 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.2.1 (user) published 188 days ago (Sat Oct 05 2024)",
"@salesforce/sfdx-scanner 4.10.0 (user) published 44 days ago (Tue Feb 25 2025) (latest is 4.11.0)",
"sfdx-plugin-source-read 1.5.0 (user) published 31 days ago (Tue Mar 11 2025) (latest is 1.5.1)",
"texei-sfdx-plugin 2.8.3 (user) published 31 days ago (Mon Mar 10 2025)"
]
}
OS: Windows 11
Experience Sites Only:
.localdev/demo/app/site/.metadata/runtime-info.json
{
"orgId": "00DH40000002d2P",
"siteId": "0DMH4000000L4PR",
"clwrVersion": "254.165",
"coreVersion": "",
"coreChangelist": "52840165",
"bundleGenerationDate": "Apr 11, 2025 9:15:31 AM",
"siteTemplateName": "microsite-template-marketing",
"deployTarget": "CORE"
}
- Langage dominant
- TypeScript
- Étoiles
- 19
- Forks
- 19
- Merge moyen
- 17 h 48 min
- PR mergées (30 j)
- 1
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de salesforcecli/plugin-lightning-dev
-
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
salesforcecli/plugin-lightning-dev#686 · 1 commentaire ·
-
Difficulté 4/5 3-5 jours Accessibilité débutants 42/100
salesforcecli/plugin-lightning-dev#627 · 2 commentaires · 1 réaction ·
-
BUG P2
Difficulté 3/5 1-2 jours Accessibilité débutants 45/100
salesforcecli/plugin-lightning-dev#544 · 4 commentaires ·
-
Difficulté 3/5 1-2 jours Accessibilité débutants 45/100
salesforcecli/plugin-lightning-dev#456 · 1 réaction ·
-
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
Toutes les issues de salesforcecli/plugin-lightning-dev
Issues similaires
-
enhancement
Difficulté 1/5 Moins d'une heure Accessibilité débutants 80/100
alunduil/projects-v2-sync#21 ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 85/100
-
enhancement minor
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
testcontainers/testcontainers-node#1539 ·
Les mainteneurs répondent en général sous 1 jour
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
christopher-buss/eslint-plugin-flawless#72 ·
Les mainteneurs répondent en général sous 1 jour
-
cleanName keeps a state code that's joined to the word before it (SavannahGa → "Savannah Ga")Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
openwatersio/slackwater-database#281 ·
Les mainteneurs répondent en général sous 1 jour