Skip to content
New issue

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

docs(script): explain expected next/script behavior on client-side navigation #42260

merged 2 commits into from Nov 2, 2022


Copy link

This PR explains that a navigation via Link would not re-execute next/script components once they are added.

Fixes #42111

Ref: slack thread


  • Related issues linked using fixes #number
  • Integration tests added
  • Errors have a helpful link attached, see


  • Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
  • Related issues linked using fixes #number
  • Integration tests added
  • Documentation added
  • Telemetry added. In case of a feature if it's used or not.
  • Errors have a helpful link attached, see

Documentation / Examples

  • Make sure the linting passes by running pnpm build && pnpm lint
  • The "examples guidelines" are followed from our contributing doc

ijjk approved these changes Nov 2, 2022
@vercel vercel bot temporarily deployed to Preview November 2, 2022 03:30 Inactive
@ijjk ijjk merged commit 460e19f into canary Nov 2, 2022
71 checks passed
@ijjk ijjk deleted the docs/clarify-next-scrpit-loading branch November 2, 2022 03:38
Copy link

It tells the behavior, but doesn't explain how to re-execute the script on client-navigation...

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

Successfully merging this pull request may close these issues.

Link tags do not populate Scripts on renavigation
4 participants