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

Issue: Local Development setup failed SfError: Error occurred downloading your site

Offen
  • Stimmt etwas nicht?
#205 15 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@nrkruk arbeitet bereits daran.

Seit 23.10.2024.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

BUG P2
Summary

Running into an issue attempting to run the local dev server for an LWR site in my scratch org.

Steps To Reproduce:
  1. run sf lightning dev site --name my_lwr_name in the cli
Expected Result

Local Dev spins up

Actual Result

Seems unable to download my LWR for an unknown reason, I've looked for more verbose logging in ~/.sf/ but could find no relevant info unfortunately

[local-dev] initializing: staff
[local-dev] Downloading site...
Local Development setup failed SfError: Error occurred downloading your site: my_lwr_name
    at ExperienceSite.downloadSite (file:///Users/kane/.local/share/sf/node_modules/@salesforce/plugin-lightning-dev/lib/shared/experience/expSite.js:203:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async LightningDevSite.run (file:///Users/kane/.local/share/sf/node_modules/@salesforce/plugin-lightning-dev/lib/commands/lightning/dev/site.js:47:27)
    at async LightningDevSite._run (/Users/kane/.local/share/sf/node_modules/@salesforce/plugin-lightning-dev/node_modules/@oclif/core/lib/command.js:301:22)
    at async Config.runCommand (/opt/homebrew/lib/node_modules/@salesforce/cli/node_modules/@oclif/core/lib/config/config.js:424:25)
    at async run (/opt/homebrew/lib/node_modules/@salesforce/cli/node_modules/@oclif/core/lib/main.js:95:16)
    at async file:///opt/homebrew/lib/node_modules/@salesforce/cli/bin/run.js:15:1 {
  actions: undefined,
  exitCode: 1,
  context: undefined,
  data: undefined,
  cause: undefined
}
System Information

Shell: Fish

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.62.6",
  "nodeVersion": "node-v20.11.1",
  "osVersion": "Darwin 24.0.0",
  "rootPath": "/opt/homebrew/lib/node_modules/@salesforce/cli",
  "shell": "fish",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.5 (core)",
    "@oclif/plugin-commands 4.1.3 (core)",
    "@oclif/plugin-help 6.2.14 (core)",
    "@oclif/plugin-not-found 3.2.22 (core)",
    "@oclif/plugin-plugins 5.4.14 (core)",
    "@oclif/plugin-search 1.2.11 (core)",
    "@oclif/plugin-update 4.6.3 (core)",
    "@oclif/plugin-version 2.2.14 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.18 (core)",
    "@oclif/plugin-which 3.2.15 (core)",
    "@salesforce/cli 2.62.6 (core)",
    "apex 3.5.1 (core)",
    "api 1.3.1 (core)",
    "auth 3.6.65 (core)",
    "community 3.0.16 (user) published 257 days ago (Sat Feb 03 2024) (latest is 3.2.35)",
    "data 3.7.0 (core)",
    "deploy-retrieve 3.12.17 (core)",
    "info 3.4.9 (core)",
    "lightning-dev 1.9.0 (user) published 6 days ago (Fri Oct 11 2024)",
    "limits 3.3.32 (core)",
    "marketplace 1.2.26 (core)",
    "org 4.6.0 (core)",
    "packaging 2.8.11 (core)",
    "schema 3.3.34 (core)",
    "settings 2.3.23 (core)",
    "sobject 1.4.41 (core)",
    "source 3.5.21 (core)",
    "telemetry 3.6.15 (core)",
    "templates 56.3.22 (core)",
    "trust 3.7.33 (core)",
    "user 3.5.32 (core)"
  ]
}

OS:
Apple M2 Pro MacOS version 15 Beta

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.