Hot reloading doesn't work and client not available.

Open
#627 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
cli, devtools

Research direction

Reproduce the problem with the listed lightning-dev installation and sf lightning dev component commands on API 66.0, then inspect the client-availability and fallback-mode logs. Done means the local client connects and changes to the generated component hot reload as expected.

Written by the indexing model from the issue text.

Description

Summary

My sandbox got upgraded to API 66.0. Local Dev either can't connect to client, or when it does doesn't hot reload anything.

Steps To Reproduce:
lightning-dev 5.1.4 (prerelease) and can't connect to client:
sf plugins install @salesforce/plugin-lightning-dev@prerelease
sf lightning generate component --name localDevTest --type lwc --output-dir force-app/main/default/lwc
sf lightning dev component --name localDevTest
Expected Result

Work properly and hot reload

Actual Result

Hot reloading doesn't work

Additional Information

Screenshots:
Image

Logs:

be1a616……0000009OXlKAM:23228 ComponentProfiler: Component-level profiling has not been enabled.
(anonymous)	@	be1a616……0000009OXlKAM:23228
ad64725……0000009OXlKAM:11749 🔵 PREVIEW MODE: previewApplication in normal mode!
ad64725……0000009OXlKAM:11785 Client not available. Running in fallback mode.
loadComponentData	@	ad64725……0000009OXlKAM:11785
System Information

SF CLI:

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.123.1",
  "nodeVersion": "node-v22.22.0"
}

OS:
macOS 26.2 (25C56)

Dominant language
TypeScript
Stars
19
Forks
19
Avg merge
3d 12h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from salesforcecli/plugin-lightning-dev

All issues in salesforcecli/plugin-lightning-dev

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.