Skip to content
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

suppressConnectErrors still results in WebSocket errors #127

Open
ethanroday opened this issue Oct 9, 2018 · 0 comments
Open

suppressConnectErrors still results in WebSocket errors #127

ethanroday opened this issue Oct 9, 2018 · 0 comments

Comments

@ethanroday
Copy link

If I pass suppressConnectErrors: true when the dev server is not running, I no longer see the SocketProtocolError messages after the first one, but I still see the WebSocket connection errors. It would be nice if these could be disabled as well.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant