-
Notifications
You must be signed in to change notification settings - Fork 569
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
Cannot read property 'WebSocket' of undefined #584
Comments
I really don't know who is guilty, but I supousse it's not your (but I can't delete the issue). I solve it changing compilerOptions in tsconfig.json from 'es2015' to 'es5' Thanks and sorry if not your fault. |
I have the same problem when using target I wonder why this error occurs because it is an important new feature of Angular 8 to compile modern js AND older js seperate if defined in browserlist. But only if you set to es2015 so it should not be changed back to es5. |
@soyjuanmedina Could you please reopen? |
Originally posted by @andy0130tw in webpack/webpack-dev-server#174 (comment) I had this problem after an upgrade to angular 8.1 and it works perfectly after doing what he suggested.
PS: with this solution, I could keep the es2015 in my tsconfig |
@loveneetabsolvetech Could you create a pull request? Or maybe someone of the contributors could fix this issue? |
I think this should be fixed by socketio/engine.io-client@357f01d (included in 3.4.1). |
Note: for support questions, please use one of these channels: stackoverflow or slack
You want to:
Current behaviour
After update my Angular App to Angular 8 I can npm start and npm build, but when I upoload to the server the console of the browser yield
Cannot read property 'WebSocket' of undefined
Other information (e.g. stacktraces, related issues, suggestions how to fix)
I really don't know if the issue is for this library, but I read the problem is about the
global.WebSocket || global.MozWebSocket;
webpack/webpack-dev-server#174 (comment)
in some libraries and I use yours
The text was updated successfully, but these errors were encountered: