You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like this library is looking for a URLSearchParams object from "svelte/reactivity", which I think no longer exists. Svelte now exports a reactive "SvelteURL".
I'm guessing the constant updates to Svelte 5 RC have broken this lib?
It looks super useful otherwise! Hard to believe Svelte doesn't have capability built in for syncing state easily with URLSearchParams.
Reproduction
Start new Svelte5 project, follow instructions from the docs. (I'm using Deno, but that shouldn't matter.)
Breaks with:
No matching export in "node_modules/.deno/svelte@5.0.0-next.259/node_modules/svelte/src/reactivity/index-client.js" for import "URLSearchParams"
node_modules/.deno/svelte-query-params@0.2.3/node_modules/svelte-query-params/dist/index.svelte.js:24:9:
24 │ import { URLSearchParams as reactive_URLSearchParams } from "svelte/reactivity";
There was a leftover todo because svelte renamed an exported class (see this release) and I was originally planning to wait until rc to make this change, but it seems it's been stable for quite a while now. This should be fixed in 0.2.4.
Describe the bug
It looks like this library is looking for a URLSearchParams object from "svelte/reactivity", which I think no longer exists. Svelte now exports a reactive "SvelteURL".
I'm guessing the constant updates to Svelte 5 RC have broken this lib?
It looks super useful otherwise! Hard to believe Svelte doesn't have capability built in for syncing state easily with URLSearchParams.
Reproduction
Start new Svelte5 project, follow instructions from the docs. (I'm using Deno, but that shouldn't matter.)
Breaks with:
No matching export in "node_modules/.deno/svelte@5.0.0-next.259/node_modules/svelte/src/reactivity/index-client.js" for import "URLSearchParams"
System Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: