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

Add a note about the existence of 'next/script' #27725

Merged
merged 4 commits into from
Aug 3, 2021

Conversation

zeekrey
Copy link
Contributor

@zeekrey zeekrey commented Aug 3, 2021

For users looking at the api reference for 'next/head' it might be a good idea to let them know that there is the 'next/script' component. Using 'next/script' has a lot of advantages over adding a script tag with 'next/head'

Documentation / Examples

  • Make sure the linting passes

For users looking at the api reference for 'next/head' it might be a good idea to let them know that there is the 'next/script' component. Using 'next/script' has a lot of advantages over adding a script tag with 'next/head'
Take @styfle 's suggestion.

Co-authored-by: Steven <[email protected]>
@kodiakhq kodiakhq bot merged commit d368f76 into vercel:canary Aug 3, 2021
flybayer pushed a commit to blitz-js/next.js that referenced this pull request Aug 19, 2021
For users looking at the api reference for 'next/head' it might be a good idea to let them know that there is the 'next/script' component. Using 'next/script' has a lot of advantages over adding a script tag with 'next/head'

## Documentation / Examples

- [x] Make sure the linting passes
@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants