BrowserStack IE error SCRIPT1002: Syntax Error
See original GitHub issueHey all,
We’ve been using:
"@bugsnag/js": "^6.0.0",
"@bugsnag/plugin-angular": "^6.0.0",
for about two months now - and recently we ran into the SCRIPT1002: Syntax Error
while testing IE11 in browserstack. Our build that had been in production was running fine with no changes, but our local instances were all running into this issue. We tracked it down to the recently released 6.3.0
version of this bugsnag library. Once we removed the ^
from the version and explicitly used version 6.0.0
it worked fine, as does 6.2.0
.
This is all I really have to provide for screenshots, the error and where the error pointed to:
This could potentially be related to #550 ?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
SCRIPT1002: Syntax error in Next JS website in IE11 ...
You need to convert it into a normal function to make it work in the IE browser. If there are multiple occurrences of...
Read more >How To Solve Script1002: Syntax Error ≪Html Lang="En ...
My code works just fine in Chrome and Edge but in IE 11, I get syntax error at line var GDN. Javascript today...
Read more >Syntax error 'SCRIPT1002' using internet explorer 11
i have tried changing versions of webpack , @wabpack/polyfill and babel-loader. but its not working. Same error i am facing in IE 11....
Read more >bootstrap-ie11 | Internet Explorer 11 compatibility solution for ...
Bootstrap 5 drops support for Internet Explorer 11, but you can add support back by simply adding a CSS file and a few...
Read more >Nuxt.js not working on IE11, throws Script1002 syntax error on ...
Like the title, says I do not what to do to make my app work on Internet Explorer 11. It works perfectly on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok – that suggests the TypeScript compiler is not transforming this module at all, perhaps due to it already being JS.
The switch fixed a different bug for users who were targetting ES6. We’ll investigate and see what we can do to solve both problems.
This is fixed as of v6.3.2 (https://github.com/bugsnag/bugsnag-js/releases/tag/v6.3.2)