Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Dev Server doesn't do anything on macOS, M1 Pro, can't be stopped neither

Offen
  • Stimmt etwas nicht?
#359 2 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
typescript
Bereich
cli, devtools

Rechercherichtung

Start by reproducing sf lightning dev app --device-type desktop --target-org jascha/supplierprice --name Customer_Manager on macOS Sequoia with the reported darwin-arm64 and zsh setup. Trace the lightning-dev command entry point and observe file-change handling and Ctrl+C shutdown; done means component changes reach the org and the server exits cleanly.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Summary

When I start the server, the Org pops up correctly, but no changes are reflected, and stopping the server is not possible

Steps To Reproduce:
  1. I start the server with sf lightning dev app --device-type desktop --target-org jascha/supplierprice --name Customer_Manager
  2. Terminal says Waiting to resolve the Lightning Experience-enabled custom domain...... done
  3. Org pops up, with a hint to a running dev server
Expected Result

When I change components, I would expect that it reflects on the org.

Actual Result

Nothing happens. Not even active reloading shows changes. So I guess the changes files aren't pushed to the server?!

Additional Information

Stopping the server isn't working too, I can type CTRL+C but nothing happens, server is stuck.

System Information

SF CLI: 2.78.3

Shell: zsh

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.78.3",
  "nodeVersion": "node-v18.19.1",
  "osVersion": "Darwin 24.3.0",
  "rootPath": "/Users/jascha/.asdf/installs/nodejs/18.19.1/lib/node_modules/@salesforce/cli",
  "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)",
    "@salesforce/lwc-dev-server 2.11.0 (user) published 1274 days ago (Wed Sep 08 2021)",
    "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 1 days ago (Mon Mar 03 2025)",
    "limits 3.3.46 (core)",
    "marketplace 1.3.7 (core)",
    "org 5.2.32 (core)",
    "packaging 1.20.1 (user) published 623 days ago (Tue Jun 20 2023) (latest is 2.10.3)",
    "schema 3.3.50 (core)",
    "settings 2.4.16 (core)",
    "signups 2.5.9 (user) published 199 days ago (Sun Aug 18 2024) (latest is 2.6.17)",
    "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)",
    "@salesforce/sfdx-plugin-lwc-test 1.2.1 (user) published 151 days ago (Fri Oct 04 2024)",
    "sfdmu 4.35.1 (user) published 198 days ago (Sun Aug 18 2024) (latest is 4.38.0)",
    "sfdx-browserforce-plugin 4.1.2 (user) published 222 days ago (Thu Jul 25 2024) (latest is 4.6.1)",
    "sfpowerkit 6.1.0 (user) published 765 days ago (Mon Jan 30 2023)",
    "texei-sfdx-plugin 2.6.1 (user) published 208 days ago (Thu Aug 08 2024) (latest is 2.8.2)"
  ]
}

OS: macOS Sequoia 15.3.1 with latest XTools

Vorherrschende Sprache
TypeScript
Sterne
19
Forks
19
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus salesforcecli/plugin-lightning-dev

Alle Issues in salesforcecli/plugin-lightning-dev

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.