chore: version packages - #77
Merged
Merged
Conversation
Deploying effex-api with
|
| Latest commit: |
2485a21
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://62e23f29.effex-api.pages.dev |
| Branch Preview URL: | https://changeset-release-main.effex-api.pages.dev |
Deploying effex with
|
| Latest commit: |
2485a21
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://80984fea.effex.pages.dev |
| Branch Preview URL: | https://changeset-release-main.effex.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@effex/router@1.3.6
Patch Changes
6651e7e: Fix browser back/forward buttons not triggering re-renders under SSG
dev mode (and any client-side navigation scenario that relies on
popstate).The
popstatehandler ran the pathname signal update viaEffect.runSync.Signal.setinternally usesSubscriptionRef.set,which acquires a semaphore permit — Effect flags that as async-capable,
so
Effect.runSyncbails silently. The event handler swallows thethrow (browsers don't reliably surface exceptions from raw event
listeners to
console.error), so the signal never actually updates,Outlet's subscribers never see the change, and the page appearsfrozen on the previous route while the URL bar shows the new one.
Fix: capture the Runtime at Layer construction time and use
Runtime.runForkto schedule the update.runForkaccepts async workand runs it on the same Runtime the rest of the app uses, so the
signal update reliably reaches subscribers even when the underlying
Signal.setisn't purely synchronous.Regression tests cover:
pathname.changes(Outlet's shape) receive thepopstate-driven change.
docs@0.0.29
Patch Changes