You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that unzipping the Linux binary inside a Docker container onto a mapped volume drive is *slow*. But once this is done you can modify the application resource folder in the local folder `/tmp/test-folder/node_modules/cypress/cypress-cache/3.3.0/Cypress/resources/app` to debug issues.
398
398
399
+
#### Docker as a performance constrained environment
400
+
401
+
Sometimes performance issues are easier to reproduce in performance constrained environments. A docker container can be a good way to simulate this locally and allow for quick iteration.
402
+
403
+
In a fresh cypress repository run the following command:
404
+
405
+
```shell
406
+
docker compose run --service-port dev
407
+
```
408
+
409
+
This will spin up a docker container based off cypress/browsers:latest and start up the bash terminal. From here you can yarn install and develop as normal, although slower. It's recommend that you run this in a fresh repo because node modules may differ between an install on your local device and from within a linux docker image.
410
+
411
+
Ports 5566 and 5567 are available to attach debuggers to, please note that docker compose run only maps ports if the `--service-port` command is used.
412
+
399
413
### Packages
400
414
401
415
Generally when making contributions, you are typically making them to a small number of packages. Most of your local development work will be inside a single package at a time.
0 commit comments