chore(docs): Add IE 11 note to v2 to v3 migration guide #37022
Merged
Conversation
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
Fix Known Issue in legacy browsers (IE 11): "Object doesn't support property or method 'setPrototypeOf'"
gatsbot
bot
added
the
status: triage needed
LekoArts
added
type: documentation
LekoArts
changed the title
LekoArts
approved these changes
Nov 14, 2022
This was referenced Nov 22, 2022
Open
Open
Open
This was referenced Nov 22, 2022
Open
Open
Open
This was referenced Nov 22, 2022
Open
Open
This was referenced Nov 23, 2022
Open
Open
This was referenced Nov 23, 2022
Open
Open
Open
Open
Open
Open
This was referenced Nov 23, 2022
Open
Open
Open
This was referenced Apr 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix Known Issue in legacy browsers (IE 11): "Object doesn't support property or method 'setPrototypeOf'"
Description
Add changes to migration guide (version 2 to 3) to outline steps for addressing a known issue when migrating to Webpack5 (a requirement for GatsbyJS v3) and targeting IE 11 legacy browser. The change describes the error displayed in browser, how to create a custom polyfill, and how to inject it into Webpack using gatsby-node.js onCreateWebpackConfig API.
Documentation
The following link describes browser support for Gatsby v3, but fails to mention this known issue:
https://v3.gatsbyjs.com/docs/how-to/custom-configuration/browser-support/#polyfills
Related Issues