We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's your version of nuqs?
nuqs
"nuqs": "^1.16.1"
Next.js information (obtained by running next info):
next info
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:43:05 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6020 Binaries: Node: 20.11.0 npm: 10.2.4 Yarn: N/A pnpm: 8.14.1 Relevant Packages: next: 14.1.1-canary.45 eslint-config-next: 14.1.0 react: 18.2.0 react-dom: 18.2.0 typescript: 5.3.3 Next.js Config: output: N/A
Are you using:
basePath
windowHistorySupport
Suffering router abort fetch errors from a page where nuqs is used. This occurs when the page is SSG and SSR. More details in this issue comment.
Update: setting the throttleMs option to 200ms "solves" the issue for me.
throttleMs
const [comparisonProductApplicationIds, setComparisonProductApplicationIds] = useQueryState( 'comparisonPAIds', parseAsArrayOf(parseAsString).withDefault([]).withOptions({ throttleMs: 200, }), )
The text was updated successfully, but these errors were encountered:
Issue was due to a bad useEffect call which was rerendering the page
useEffect
Sorry, something went wrong.
No branches or pull requests
Context
What's your version of
nuqs
?Next.js information (obtained by running
next info
):Are you using:
basePath
option in your Next.js configwindowHistorySupport
flag in your Next.js configDescription
Suffering router abort fetch errors from a page where nuqs is used. This occurs when the page is SSG and SSR. More details in this issue comment.
Update: setting the
throttleMs
option to 200ms "solves" the issue for me.Reproduction
The text was updated successfully, but these errors were encountered: