Cypress component tests in monorepo problems with typescript #31933
Replies: 1 comment
-
The tsconfig was only an assumption by me. The real problem was a completely different one, where I referenced wrong support files, which were leftovers of my Monorepo changes done pretty recently. So this whole question was pretty non-sense |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello guys! I have some problems with a previously working cypress component test setup, since switching to a monorepo structure.
To avoid overhead, I decided to put my cypress setup in my consuming app, where I did not change anything to the previous version. I then extended my
cypress.config.ts
to find the specs in my packages, which worked fine. The specs living in my packages do also work fine and are being executed as previously. But the specs living in my consuming app are not being exectued correctly. With following errorWhich looks like typescript problems. My
tsconfig.json
files do differ in the consuming app and my package, which is why I think it has something to do with my ts setup. Following my configs for reference:Working one:
Broken one:
What did I try? I did try to follow the docs article on typescript and cypress, but when I utilize a
tsconfig.json
in my cypress directory, the same way it is done in the RWA example, no cypress types are recognized. The same happens when I checkout the RWA example and boot it in my vscode.Would be grateful for any help. I admit being some kind of beginner if it comes to ts. I can write code, but some depths are still hidden to me.
Beta Was this translation helpful? Give feedback.
All reactions