Thank you for your pull request! Please provide the following information.
Change Description:
A misspelling was causing the polyfill generation to be incorrect and projects wouldn't work with the IE webview as a result. Corrected the reference to the entries in webpack config and the adjusted a component compatibility problem that was hidden behind that lack of polyfills
Do these changes impact any npm scripts commands (in package.json)? (e.g., running 'npm run start')
No.
Do these changes impact VS Code debugging options (launch.json)?
No.
Do these changes impact template output? (e.g., add/remove file, update file location, update file contents)
No.
Thank you for your pull request! Please provide the following information.
Change Description: A misspelling was causing the polyfill generation to be incorrect and projects wouldn't work with the IE webview as a result. Corrected the reference to the entries in webpack config and the adjusted a component compatibility problem that was hidden behind that lack of polyfills
Do these changes impact any npm scripts commands (in package.json)? (e.g., running 'npm run start') No.
Do these changes impact VS Code debugging options (launch.json)? No.
Do these changes impact template output? (e.g., add/remove file, update file location, update file contents) No.
Do these changes impact documentation? (e.g., a tutorial on https://docs.microsoft.com/en-us/office/dev/add-ins/overview/office-add-ins) No.
If you answered yes to any of these please do the following:
Validation/testing performed: Tried resulting changes on a machine running an older version of office that uses the IE webview explicitly.