-
Notifications
You must be signed in to change notification settings - Fork 3k
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
MS Edge fails with SCRIPT1028: Expected identifier, string or number #3339
Comments
With this issue without isolation in build steps, I have suspect this is related to your build configurations. Specific code line you mentioned is simply transpiled down into like below: (CJS, umd both)
while having If you can't strip out code, what happens if you import bare rx without involving anything in Edge? (no angular, no polymer, etcs) |
Also may worth to check http://reactivex.io/rxjs/ (it loads umd build of Rx inside) on Edge to see global build fails with same transpiled results. (it did work on me). |
The code looks like this:
|
Downgrading the transpile to es5 works around the problem. |
I'm feeling it'd better to rename variable name in further eventually, for cases if we have runtime doesn't need any transpilation one day. |
Problem still occurs in RxJS 6.1.0 |
Just run at this problem too. For me |
Ran into this problem with Angular 8 and Edge. Same code piece as above. |
Since old EDGE itself is deprecated, closing issue and recommend to use latest rxjs & support chromium based edge. |
RxJS version:
5.5.6
Code to reproduce:
N/A, we have a complicated build process, can't strip out the code to repro.
Angular5, webpack, Polymer, etc.
Expected behavior:
RxJS should work in MS Edge
Actual behavior:
SCRIPT1028: Expected identifier, string or number
App fails to render anything, blank page.
Additional information:
After a short investigation, the problem is on this line (marked with * the exact position):
This line is the part of the AjaxSubscriber class' send() method.
If I replace the 'async' variable names in the method for eg. 'asynch', everything starts to work without any problem.
The text was updated successfully, but these errors were encountered: