-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Typescript example recipe workflow #1356
Comments
I know we currently watch the file for changes - after you introduce an error and then revert the problem (and get back to working code) does it automatically update or do you have to click "Try Again" ? |
Yeah, had the same thought. For me, it's stopped watching. I always have to click try again even when the compilation error has been resolved. |
Closing as resolved. If you're experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix. |
Current behavior:
Using the Webpack with Typescript example recipe, Typescript compilation issues cause the plugin to crash. This brings you to the following screenshot.
(Image edited to remove sensitive information)
Additionally, the Try Again button on the Cypress app is at the bottom of the error message. When the error is quite lengthy, I spend a decent amount of time scrolling or using keyboard shortcuts to get to the bottom of the window so that I can click the Try Again button.
Desired behavior:
The plugin doesn't crash due to compilation issues. It keeps monitoring for changes and the Typescript compilation issues are displayed in the running browser session.
The Try Again button remains above the error message to reduce the time needed to restart the plugin.
How to reproduce:
Using the Webpack with Typescript recipe, add random text to the spec file such that the text cannot be resolved as a valid command or statement.
The text was updated successfully, but these errors were encountered: