Skip to content

Version Packages (next)#995

Merged
davedbase merged 1 commit into
nextfrom
changeset-release/next
Jul 20, 2026
Merged

Version Packages (next)#995
davedbase merged 1 commit into
nextfrom
changeset-release/next

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

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 next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@solid-primitives/focus@1.0.0-next.2

Minor Changes

  • b7ef2f3: Add createFocusRestore — saves the currently focused element while active and restores focus to it once deactivated, without trapping focus or managing tab order. For non-modal surfaces (Popover, Tooltip, Menu) that should return focus to their trigger on close but must not intercept Tab navigation while open; for modal dialogs needing both behaviors, use createFocusTrap's existing restoreFocus option instead.

    Also fixed a stale-closure race shared between createFocusTrap and the new createFocusRestore: the restore target used to be read from a mutable outer variable inside a deferred afterPaint callback, so a fast reactivate-before-restore-fires cycle could restore focus to the wrong element. Both primitives now share one internal helper that captures the target synchronously at deactivation time.

Patch Changes

  • Updated dependencies [b7ef2f3]
    • @solid-primitives/utils@7.0.0-next.3

@solid-primitives/interaction@1.0.0-next.3

Minor Changes

  • b7ef2f3: createHideOutside/ariaHideOutside gain an opt-in inert option — in addition to aria-hidden, also sets the inert attribute on hidden elements, ref-counted alongside aria-hidden. aria-hidden alone only affects the accessibility tree; inert additionally removes hidden content from focus order, tab order, and pointer/text-selection interaction. Defaults to false (no behavior change for existing callers).

    Also hardened the module-scope ref-counting/observer-stack state (used internally by both the existing aria-hidden tracking and the new inert tracking) against duplicate installed copies of this package, via the same globalRegistry pattern used in @solid-primitives/scroll.

Patch Changes

  • Updated dependencies [b7ef2f3]
    • @solid-primitives/utils@7.0.0-next.3

@solid-primitives/utils@7.0.0-next.3

Minor Changes

  • b7ef2f3: Add globalRegistry(key, init) — returns a singleton value keyed by key on globalThis (via Symbol.for), shared across every copy of the calling module loaded in the same JS realm. Use it instead of a plain module-scope let/const for state (ref-counts, active-instance stacks) that must stay consistent even if the app's dependency graph ends up with more than one installed copy of a package.

@solid-primitives/a11y@1.0.0-next.2

Patch Changes

  • b7ef2f3: createFormControl's dataset accessor is now a plain getter instead of a createMemo — no behavior or type change, but it removes an unnecessary render-body compute-form memo (memoizing a handful of cheap string/undefined fields buys nothing) that would otherwise consume a hydration id in every consuming app.
  • Updated dependencies [b7ef2f3]
    • @solid-primitives/utils@7.0.0-next.3

@solid-primitives/controlled-props@1.0.0-next.2

Patch Changes

  • b7ef2f3: BoolProp, NumberProp, RangeProp, and StringProp are now typed VoidComponent instead of Component, since none of them accept or render children. Type-only change, no behavior difference.
  • Updated dependencies [b7ef2f3]
    • @solid-primitives/utils@7.0.0-next.3

@solid-primitives/intersection-observer@3.0.0-next.2

Patch Changes

  • b7ef2f3: Fix isVisible()/createVisibilityObserver()'s visible() throwing a locally-defined NotReadyError lookalike class instead of the real one exported from solid-js. Because the local class wasn't instanceof the real NotReadyError, <Loading> boundaries never actually caught it — despite the documented <Loading> integration, calling isVisible/visible before the first observation would crash rendering instead of showing the Loading fallback. NotReadyError is now imported and re-exported from solid-js directly, so <Loading> (and any instanceof check) works as documented.
  • Updated dependencies [b7ef2f3]
    • @solid-primitives/utils@7.0.0-next.3

@solid-primitives/notification@1.0.0-next.2

Patch Changes

  • b7ef2f3: createNotificationPermission's requestPermission now calls affects(permission), so isPending(permission) reads true for the duration of the request — the standard Solid 2.0 idiom for callers who don't want the existing bespoke pending accessor, which is unchanged and kept for backward compatibility.
  • Updated dependencies [b7ef2f3]
    • @solid-primitives/utils@7.0.0-next.3

@solid-primitives/scroll@3.0.0-next.2

Patch Changes

  • b7ef2f3: createPreventScroll's active-instance stack and body-style ref-counts now live in a globalRegistry (keyed on globalThis, not module-scope bindings), so they stay correct even if the app's dependency graph ends up with more than one copy of this package installed — module-scope state would otherwise be split across copies, breaking the "topmost instance" ref-counting. Also replaced a hand-rolled contains() helper with the equivalent one already exported from @solid-primitives/utils. No API changes.
  • Updated dependencies [b7ef2f3]
    • @solid-primitives/utils@7.0.0-next.3

@solid-primitives/spring@1.0.0-next.2

Patch Changes

  • Updated dependencies [b7ef2f3]
    • @solid-primitives/utils@7.0.0-next.3

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying solid-primitives with  Cloudflare Pages  Cloudflare Pages

Latest commit: 8ee8b7a
Status:🚫  Build failed.

View logs

@davedbase
davedbase merged commit 6cad3b0 into next Jul 20, 2026
1 check failed
@davedbase
davedbase deleted the changeset-release/next branch July 20, 2026 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant