Error: "Local Development setup failed SfError: No published site found for: Test Local Dev"
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- cli
Research direction
Start with the downloadSite call in expSite.js and the LightningDevSite.run entry point in site.js named by the stack trace. Reproduce the sf lightning dev site command against a sandbox with a published Build Your Own LWR site, then inspect how the site is located. Done means the command recognizes the published site and shows its local preview instead of reporting that no published site was found.
Written by the indexing model from the issue text.
Description
Summary
Error "Local Development setup failed SfError: No published site found for" when I try to run the sf lightning dev site command on my sandbox org.
Steps To Reproduce:
- Enable Local Dev on sandbox org.
- Create a new LWR site with the "Build Your Own (LWR)" template
- Publish the new site
- Run
sf lightning dev sitecommand
Expected Result
Should run the command and show the site preview.
Actual Result
Getting error "Local Development setup failed SfError: No published site found for".
Additional Information
Screenshots:
Logs:
[config] peer dependency pwa-kit-runtime was not provided
[local-dev] initializing: Test Local Dev
Local Development setup failed SfError: No published site found for: Test Local Dev
at ExperienceSite.downloadSite (file:///C:/Users/Admin/AppData/Local/sf/node_modules/@salesforce/plugin-lightning-dev/lib/shared/experience/expSite.js:189:19)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async LightningDevSite.run (file:///C:/Users/Admin/AppData/Local/sf/node_modules/@salesforce/plugin-lightning-dev/lib/commands/lightning/dev/site.js:47:27)
at async LightningDevSite._run (C:\Users\Admin\AppData\Local\sf\node_modules\@salesforce\plugin-lightning-dev\node_modules\@oclif\core\lib\command.js:301:22)
at async Config.runCommand (C:\Users\Admin\AppData\Local\sf\client\2.78.3-b3024dd\node_modules\@oclif\core\lib\config\config.js:456:25)
at async run (C:\Users\Admin\AppData\Local\sf\client\2.78.3-b3024dd\node_modules\@oclif\core\lib\main.js:96:16)
at async file:///C:/Users/Admin/AppData/Local/sf/client/2.78.3-b3024dd/bin/run.js:15:1 {
actions: undefined,
exitCode: 1,
context: undefined,
data: undefined,
cause: undefined
}
System Information
SF CLI:
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.78.3",
"nodeVersion": "node-v22.13.1",
"osVersion": "Windows_NT 10.0.22631",
"rootPath": "C:\\Users\\Admin\\AppData\\Local\\sf\\client\\2.78.3-b3024dd",
"shell": "cmd.exe",
"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)",
"community 3.3.11 (user) published 21 days ago (Sat Feb 08 2025) (latest is 3.3.14)",
"data 4.0.11 (core)",
"deploy-retrieve 3.20.0 (core)",
"info 3.4.39 (core)",
"lightning-dev 1.10.0 (user) published 71 days ago (Fri Dec 20 2024)",
"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: Windows 11
- 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 72/100
0xMiden/bridge-portal#132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:tools bug good first issue help wanted priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
TaewoooPark/Motifcode#14 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
newrelic-experimental/preflight#793 · 1 comment ·