-
Notifications
You must be signed in to change notification settings - Fork 22
Crashes when preprocessing 24 Typescript tests (but sometimes works) #79
Comments
Maybe useful observation. I can get all the tests to preprocess and run if I do this:
So its clicking "Run all specs" that seems to send the software down a weird path. |
Sorry, the above statement is bogus. The tests ran when I tried that just because sometimes they do. |
@mike-hogan You shouldn't need to use a preprocessor for TypeScript since Cypress 4.4.0. Have you tried removing this altogether? |
Thanks @jennifer-shehane . When I remove the preprocessor, I get this error message:
The offending line is isColoured() {
return this.getColourSource().getPropertyId() !== null;
} My IDE, tsc and the preprocessor are all fine with this line, and I don't see any more explanatory error messages any place. How do you recommend I proceed? Thanks. |
Looks like @chrisbreiding opened an issue about the error your encountering now cypress-io/cypress-browserify-preprocessor#47 |
The |
"@cypress/webpack-preprocessor": "^5.1.2",
"ts-loader": "^7.0.1",
"typescript": "^3.8.3",
"webpack": "^4.43.0"
Current behavior:
npx cypress open
[1] Here is what I was referring to as a lot of output streaming:
If I do the above 4 or 5 or 6 times, sometimes all the tests come up in the GUI and I can run them all. We're talking about 24 tests, none of which are especially long or complex.
Desired behavior:
Tests preprocess and run in the GUI
How to reproduce:
As per above
Additional Info (images, stack traces, etc)
Here is my plugins/index.js:
Here is my tsconfig.json:
This is my cypress.json:
The text was updated successfully, but these errors were encountered: