Closed deluksic closed 1 year ago
Sorry about not using StackBlitz for this case, but I was not able to reproduce in that environment. Seems like they do something fancy with auto-saving.
@deluksic I am preparing a PR with a fix for this at this very moment :).
Fixed by #27
Describe the bug
Modifying a component does not result in updated DOM.
EDIT: I'm not sure this is
solid-js
issue, however I believe it is reasonable to start here and then see ifvite
is the culprit.Your Example Website or App
https://github.com/deluksic/solid-fast-refresh-repro
Steps to Reproduce the Bug or Issue
ORDER OF OPERATIONS IS IMPORTANT!!
1) run the server and open in the browser.
2) modify and save
Sub.tsx
, counter should not increase, changes are applied. 3) saveApp.tsx
, counter should increase by 1. 4) modifySub.tsx
, observe no changes in the browser.From then on, saving
App.tsx
will correctly use most recentSub.tsx
, but savingSub.tsx
will not rerender the component.Expected behavior
After those steps, I'm expecting to see changes applied to the DOM after modifying
Sub.tsx
.Platform