Forum Discussion

DusteJ's avatar
DusteJ
Copper Contributor
Apr 30, 2019

Running into issue with SPFX recently Cannot redefine non-configurable property 'startsWith'

I am running into below issue when I try configuring SPFX control on Modern Page, this particular control was working fine without any issue up until now.

 

Something went wrong

If the problem persists, contact the site administrator and give them the information in Technical Details.
Technical Details
[SPLoaderError.loadComponentError]:
***Failed to load component "11111111-2017-4bc3-9a39-18dfdd167e1b" (DocumentNavigationWebPart).
Original error: ***Failed to load entry point from component "11111111-2017-4bc3-9a39-18dfdd167e1b" (DocumentNavigationWebPart).
Original error: Error loading https://component-id.invalid/11111111-2017-4bc3-9a39-18dfdd167e1b_0.0.1
 Cannot redefine non-configurable property 'startsWith'

***INNERERROR:
***Failed to load entry point from component "11111111-2017-4bc3-9a39-18dfdd167e1b" (DocumentNavigationWebPart).
Original error: Error loading https://component-id.invalid/11111111-2017-4bc3-9a39-18dfdd167e1b_0.0.1
 Cannot redefine non-configurable property 'startsWith'
***CALLSTACK:
Error
   at t._generateErrorStackForIE (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:294:16395)
   at t (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:294:15931)
   at t (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:1171:21147)
   at e.buildErrorWithVerboseLog (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:1171:16208)
   at e.buildLoadComponentError (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:1171:12233)
   at Anonymous function (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:1171:61148)
   at L (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:8:2116)
   at T (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:8:2232)
   at O (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:8:2026)
   at g (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-04-19.008/sp-webpart-workbench-assembly_en-us_9054ac0820813d004dc54250095f82c4.js:8:1608)

 

5 Replies

Sort By
  • Freddy Bang's avatar
    Freddy Bang
    Copper Contributor
    May 02, 2019

    DusteJ and Paul Bevis we have resolved the issue in our SPFX web parts simply by removing this line:

    import 'core-js/es6/string';
     
    After an update done by Microsoft this week it seems that SharePoint Online now adds string polyfill automatically. Polyfill is used to support "old" browsers like IE11 which does not support many features of javascript.
     
    So our conclusion is that the Issue were connected with polyfills and changes done by Microsoft this week..
  • Paul Bevis's avatar
    Paul Bevis
    Brass Contributor
    May 01, 2019
    Same issue here. Only affects IE11. Works fine in the Workbench but our production site is down. It been working for ages, looks like Microsoft may have changed something.

Resources