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.

Sign up for GitHub

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

Jump to bottom

Clarify in docs that next/script must not be in next/head #27534

Merged
merged 6 commits into from
Aug 1, 2021
Merged

Clarify in docs that next/script must not be in next/head #27534

Changes from 5 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
b47de7d
Clarify in docs that `next/script` must not be in `next/head`
zackdotcomputer Jul 27, 2021
a350602
Apply suggestions from @styfle's code review
zackdotcomputer Jul 27, 2021
15d30ca
Merge branch 'canary' into clarify-script-head-docs
zackdotcomputer Jul 28, 2021
94ce981
Remove extraneous sentence from caution note
zackdotcomputer Jul 31, 2021
23f07e5
Merge branch 'canary' into clarify-script-head-docs
zackdotcomputer Jul 31, 2021
176ac4e
Merge branch 'canary' into clarify-script-head-docs
kodiakhq[bot] Aug 1, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/basic-features/script.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,11 @@ export default function Home() {
}
```

With `next/script`, you no longer need to wrap scripts in `next/head`. Further, `next/script` should **not** be used in `pages/_document.js` as `next/script` has client-side functionality to ensure loading order. For example:
Now, you use `next/script` in the body of your Next.js page. It has client-side functionality that decides when and how to load the remote script based on the `strategy`.

> **Note:**
>
> - `next/script` **must not** be placed in either a `next/head` component or in `pages/_document.js`.

```js
// After
Expand Down