Dev Server continuously hot-reloads if js files are imported form subfolder

Open
#544 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js, typescript
Domain
cli, devtools

Research direction

Start with the sf lightning dev component --name sample entry point and reproduce the watcher loop using a Lightning web component that imports a JavaScript file from a subfolder. Compare the change-detected events with the generated local code and determine why the server reloads repeatedly. Done means the component loads local code once without a continuous reload cycle; add or run the relevant watcher test if one is found.

Written by the indexing model from the issue text.

Description

BUG P2
Summary

I have a lightning web component and use sf lightning dev as local dev server.
I split the js code of the web component into multiple files are try to organize them in folders

when I do this, the dev server starts but gets a 'change detected' signal about each second

Image

The lighting compiler that is used when 'deploy'ing and the one producing the code works as expected

Steps To Reproduce:
  • Create an lwc
  • factor out code from the main js file , move it into a subfolder and import it from there
  • start the dev server and look at the console output
Expected Result

The component should be loaded from backend, then one-time replaced by the local code and displayed

Actual Result

the component loads form the backend, but then a reload cycle of the local code occurs around each second

Additional Information

Screenshots:
see above

Logs:
see screenshot. I could produce debug logs if needed. Would be nice to know how to set DEBUG to a value other than '*' to limit the output to the really necessary (e.g. excluding babel output)

System Information

SF CLI:

sf lightning dev component --name sample

sf --version

@salesforce/cli/2.109.6 win32-x64 node-v22.19.0

sf plugins

code-analyzer 5.5.0
lightning-dev 4.5.2

Uninstalled JIT Plugins:
community 3.3.41
custom-metadata 3.3.68
dev 2.5.1
devops-center 1.2.27
flow 1.0.2
signups 2.6.49
@salesforce/sfdx-plugin-lwc-test 1.2.1

OS:
Windows

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.