-
Notifications
You must be signed in to change notification settings - Fork 23
Comparing changes
Open a pull request
base repository: solidjs/solid-refresh
base: main
head repository: solidjs/solid-refresh
compare: next
- 16 commits
- 46 files changed
- 1 contributor
Commits on Mar 2, 2026
-
feat: Solid 2.0 compatibility + transparent HMR memo
- Add transparent: true to HMRComp's createMemo so HMR wrapper doesn't shift hydration IDs - Fix createSignal to avoid Solid 2.0 function-as-compute-fn overload - Fix createMemo signature (options now 3rd arg in Solid 2.0) - Unify context HMR with component HMR (Context IS a component in Solid 2.0) - Remove separate $$context path, route through $$component with .id preservation - Update to solid-js@2.0.0-experimental.16 and babel-preset-solid@2.0.0-experimental.16 - Bump version to 0.8.0-next.0 Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for 6346faa - Browse repository at this point
Copy the full SHA 6346faaView commit details
Commits on Mar 3, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 2b4dcef - Browse repository at this point
Copy the full SHA 2b4dcefView commit details -
fix: Solid 2.0 compatibility for HMR runtime
- Use createSignal(fn) for synchronous component initialization (batched writes) - Wrap source() guard in untrack() to avoid reactive tracking warning - Update devDependencies and peerDependencies to Solid 2.0 experimental - Bump to 0.8.0-next.1 Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for 74e9888 - Browse repository at this point
Copy the full SHA 74e9888View commit details -
fix: prevent stale closure in writable memo when computed goes LAZY
createSignal(() => component) creates a computed node that captures the original component in its closure. When all subscribers are disposed (e.g. component unmounted by Show), the computed goes LAZY. On next read, re-evaluation runs the closure and returns the stale original value, discarding the setter's update. Fix: use a mutable `current` variable in the closure so re-evaluation always returns the latest component set via patchComponent. Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for 7d7b357 - Browse repository at this point
Copy the full SHA 7d7b357View commit details -
update solid-js and babel-preset-solid to beta release
Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for 12a63ae - Browse repository at this point
Copy the full SHA 12a63aeView commit details
Commits on Mar 4, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 4c96f76 - Browse repository at this point
Copy the full SHA 4c96f76View commit details -
update solid deps to beta and restrict peer dep to prereleases
Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for c34adeb - Browse repository at this point
Copy the full SHA c34adebView commit details -
Configuration menu - View commit details
-
Copy full SHA for ce0bee8 - Browse repository at this point
Copy the full SHA ce0bee8View commit details
Commits on Mar 10, 2026
-
fix: pass strictRead label to untrack in HMR proxy
Use untrack(fn, label) instead of separate setStrictRead calls, matching the updated API in @solidjs/signals where strictRead is now an optional parameter on untrack. Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for 8edf4d0 - Browse repository at this point
Copy the full SHA 8edf4d0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 69d013f - Browse repository at this point
Copy the full SHA 69d013fView commit details
Commits on Mar 12, 2026
-
fix: untrack source() reads in proxy traps to suppress false strict-r…
…ead warnings The proxy get/set traps read source() which triggered "top level read" warnings in dev mode when accessed inside a strictRead context. These reads were already non-reactive in practice (component bodies run inside untrack), so wrapping with untrack() suppresses the false positive without any behavioral change. Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for c8f0620 - Browse repository at this point
Copy the full SHA c8f0620View commit details -
Configuration menu - View commit details
-
Copy full SHA for 27651bd - Browse repository at this point
Copy the full SHA 27651bdView commit details
Commits on Mar 21, 2026
-
fix: use stable transform name for strictRead label instead of functi…
…on .name Bundlers like esbuild (used by Vite) can rename function expressions to avoid shadowing (e.g. function Counter -> Counter2), which caused the strictRead warning label to show mangled names. Use the name parameter from the babel transform which is always the correct identifier. Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for 3ce2e04 - Browse repository at this point
Copy the full SHA 3ce2e04View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1856453 - Browse repository at this point
Copy the full SHA 1856453View commit details
Commits on Mar 28, 2026
-
fix: recognize @solidjs/web render imports
Treat Solid 2's @solidjs/web entrypoint as the canonical render import so refresh cleanup hooks still attach. Update the mirrored transform tests and snapshots to reflect the new import source. Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for d52cf49 - Browse repository at this point
Copy the full SHA d52cf49View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9fe9d53 - Browse repository at this point
Copy the full SHA 9fe9d53View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...next