-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
fix(next): improve error for using <Html> outside of document #45056
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
21e8366
fix(next): improve error for using <Html> outside of document
JoshuaKGoldberg d806849
Merge branch 'canary' into safe-html-context
JoshuaKGoldberg 2ab53d9
Merge branch 'canary' into safe-html-context
JoshuaKGoldberg 76cfe99
Merge branch 'canary' into safe-html-context
ijjk c31f2cb
Merge branch 'canary' into safe-html-context
kodiakhq[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yet another case where
as any
is a Bad 😈Explaining:
createContext
is a hard API to get type safe. Its typings indicate that you must provide a default value for it: that way, when it's called, it's known to always return a value. (In more technical terms,createContext<T>
takes in a parameter of typeT
so the return type isT
, notT | undefined
.)Unfortunately that means that when there isn't a reasonable default value -the majority of the time in my experience 🙃- projects tend to provide something bogus like
null as any
to get around type checking. They then assumeuseContext
will only be called with that context in places where someone has used that context's provider to provide a real value.The assumption that someone's provided an overridden value isn't always correct! We see in this PR's linked bug #45024 that if someone renders
<Html>
outside ofpages/_document.(js|tsx)
, Next.js hasn't provided a context value withHtmlContext.Provider
. So when code triesconst { ... } = useContext(HtmlContext)
, that evaluates toconst { ... } = undefined
, which is a runtime error.This PR doesn't change whether an error is thrown. It just throws a nicer error for users to read.