Update next/script docs to clear up confusion around next/head and client-side JS

[timneutkens]

Bug

• Related issues linked using fixes #number
• Integration tests added

Feature

• 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.

Documentation / Examples

Fixes #26187
Fixes #26158

• Make sure the linting passes

[Vadorequest]

The doc has changed and I understand better the issue now, but the eslint rule might need to be reviewed, too.

[timneutkens]

The doc has changed and I understand better the issue now, but the eslint rule might need to be reviewed, too.

Can you share what part exactly? Happy to have a look!

[Vadorequest]

@timneutkens If you add a script tag within a NextJS Head element, it'll warn.

Considering the documentation update, this behavior is likely to push devs to use Script there instead, although it shouldn't be used there.

[timneutkens]

In the case that you're showing you should use <Script> with the right strategy 🤔

[Vadorequest]

If I do that, I ran into the Cannot read property 'tagName' of null error.

NextHead (line 91) is next/head component, maybe that wasn't clear.

[timneutkens]

The docs linked show to not wrap next/head right 🤔

[Vadorequest]

Yes, the doc say not to use Script component when wrapping with next/head. I'm wrapping with next/head, so I shouldn't use the Script component, but ESLint will complain if I don't.

[timneutkens]

This docs update means don't put it inside of next/head not "if you're using <script> in next/head". In all cases next/script is recommended.