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

Aperta
#544 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
javascript, node.js, typescript
Ambito
cli, devtools

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
19
Fork
19
Merge medio
3g 12h
PR unite (30g)
2

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di salesforcecli/plugin-lightning-dev

Tutte le issue di salesforcecli/plugin-lightning-dev

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.