-
## What component is this related to?
Cypress testing
## Why do we need it?
Once the Cypress custom commands have been exposed within the React package, this will need to be communicated to the c…
jd239 updated
3 months ago
-
### Current behavior
Here's a very ambiguous CI issue during parallelization
It happens because Chrome rolls out varying versions , and if the parallelized CI machines do not match versions, you…
-
We should migrate Cypress to version 10.x to support React v18.x and to use the newest features of cypress.
I would suggest to remove Cypress from the master branch, so we can use React v18.x and M…
-
I was only able to reproduce this issue using cypress,
```
(uncaught exception)Error: Hydration failed because the initial UI does not match what was rendered on the server.
(uncaught exception)E…
-
### Current Behavior
Whenever I run the `build-storybook` task on a `vite` generated library, it copies the files from `nxCopyAssetsPlugin` call in `vite.config.ts` to
```
/Users/{user}/path/to/mono…
-
### Current behavior
When trying to interact with an element rendered by React that has `htmlFor` set to an ID returned by the `useId()` hook, the peculiar syntax React uses for IDs in React 18 act…
-
We would like to add Cypress https://www.cypress.io/ to the project and write some automation tests.
-
Feature Request. I'm currently running cypress using the following configuration. Is there a way to hook into the existing CRA `start` process and not have to setup `serve` to do this. This works but …
-
### Current Behavior
Error: warning ../../../../package.json: No license field
error Command failed with exit code 1
### Expected Behavior
The Nx workspace should be successfully created without er…
-
I'm upgrading to Vue 3 via Nuxt 3, which pretty much forces me into Vite. (I wish it weren't so.)
I'd like to maintain code coverage. I think this package is the only way to get cypress code covera…