Skip to content

upgrade: geolocation package upgrade for Solid 2.0#841

Draft
davedbase wants to merge 26 commits intosolidjs-community:nextfrom
davedbase:update/v2/geolocation
Draft

upgrade: geolocation package upgrade for Solid 2.0#841
davedbase wants to merge 26 commits intosolidjs-community:nextfrom
davedbase:update/v2/geolocation

Conversation

@davedbase
Copy link
Copy Markdown
Member

Proposal for upgrading to Solid 2.0 which includes:

  • Added makeGeolocation(options?) — non-reactive one-shot query returning [query, cleanup] tuple, no Solid owner required
  • Added makeGeolocationWatcher(options?) — non-reactive continuous watcher returning [store, cleanup] tuple, no Solid owner required
  • createGeolocation now returns [Accessor<GeolocationCoordinates>, refetch] — async memo that suspends with <Suspense>, re-queries when reactive options change or refetch() is called. Supports isPending() for background re-query indicators
  • createGeolocationWatcher now returns { location: Accessor<GeolocationCoordinates>, error: Accessor<GeolocationPositionError | null> }location suspends until the first GPS fix then updates reactively; error is a signal for recoverable in-component error handling
  • Replaced createResource with async createMemo + version signal
  • Replaced createComputed with createEffect
  • Updated peer dependency to solid-js@^2.0.0

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 15, 2026

🦋 Changeset detected

Latest commit: fd0191a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@solid-primitives/geolocation Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@davedbase davedbase marked this pull request as draft April 20, 2026 02:14
@davedbase davedbase changed the base branch from main to next April 21, 2026 01:47
@davedbase davedbase added this to the Solid 2.0 Upgrade milestone Apr 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants