Readme: Add Astro example #771
Conversation
tordans
changed the title
|
@tordans is attempting to deploy a commit to the 47ng Team on Vercel. A member of the Team first needs to authorize it. |
|
Thanks! Eric Burel also pointed out nanostores for shared Astro state on Bluesky: https://bsky.app/profile/francoisbest.com/post/3lah564mkmd2w Unlike the other adapters, I'm not actually sure the React adapter would work if two of them were added as siblings (eg: in different islands), as they don't yet have a way to re-render when the URL changes via external means (eg: an explicit call to the history API, or another island doing a setState on a useQueryState). If they were to be loaded in memory multiple times (code-split per island rather than made into a common chunk), the separate event emitters would also not be able to sync the internal states across islands. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I am testing out nuqs with an Astro app and it looks like all works great (*).
This example for the Readme shows a possible way to use it.
The thing that is different for Astro is, that there is no "Root" to place the
NuqsAdapterIMO, since each Astro island is independent. Which is why we need to do this semi-elegant wrapper component.There might be better ways to do this, though.
(*) (!) However, I did not test (yet) how this behaves with multiple islands and
NuqsAdapters. This could very well break the setup. Until now I used the recommended nanostore in those cases. See https://docs.astro.build/en/recipes/sharing-state-islands/However, nanostore remove the nuqs like helper methods at some point. More on this is in nanostores/router#30. My previous workaround was to use a copy of the removed helper, eg. osmberlin/www.osm-verkehrswende.org@3d2e27b#diff-acaaec4d6340f096b1c5dab9c107023b24ec701667fa9c9bb362fdf9e92ce846R55
I will mark this as a draft for now until the
(!)is cleared up.