chore: version packages - #79
Merged
Merged
Conversation
Deploying effex-api with
|
| Latest commit: |
ce17a7f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://137401b3.effex-api.pages.dev |
| Branch Preview URL: | https://changeset-release-main.effex-api.pages.dev |
Deploying effex with
|
| Latest commit: |
ce17a7f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://98b59c35.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
1 participant
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
create-effex@1.1.2
Patch Changes
client.ts): was callinghydrate(App(), root)with nolayers, even though the App uses
OutletandLinkwhich requireNavigationContext. Hydration bailed as soon as either was resolved.Now passes
Platform.makeClientLayer(router)viaoptions.layers.main.ts): passed{ layers: ... }as a third arg tomount, which doesn't accept options — the arg was silently droppedand the returned
Effectwas never run, so nothing mounted at all. Nowuses
runApp(mount(...), { layer: ... }), the documented pattern.@effex/dom@1.4.6
Patch Changes
49af20d: fix(hydrate): build
options.layersin the outer program scopePreviously
hydrateusedEffect.provide(element, elementLayers), whichinternally wraps the effect in a fresh scope that closes as soon as the
effect completes. Since element functions return synchronously after
building the DOM, this tore down every scoped resource — Navigation's
popstate listener,
SubscriptionRefPubSub subscribers, cache entries —before the user could interact. Browser back/forward, reactive updates,
and anything relying on
Effect.addFinalizersilently no-op'd.Fixed by building the merged layers as a
Contextin hydrate's outerprogram scope (kept alive by
Effect.never) before providing.@effex/router@1.3.7
Patch Changes
docs@0.0.30
Patch Changes