cypress
cypress copied to clipboard
chore: added dev container
As someone who works/contributes to dozens of projects, I dislike installing all dev-tools needed for all projects on a single machine. Fortunately, there are Dev Containers, which allow to build a whole dev-environment inside containers and with correct X11 forwarding (eg. by default with WSL2), even allows to use UI apps in the container and display them.
This PR adds initial support for a dev-container, which allows building, testing and even running Cypress from inside the container. It will not affect anyone not using dev-containers at all but allows those who want to use it.
It probably needs some fine-tuning and adjustments (eg. I had to set chrome-sandbox to root and chmod 4755) which might be fixed in other ways, but it is a start and works and allows improving it further if people use it and give feedback.
- Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
@Roemer would it work for M1 macs / ARM based dev environments if the AMD64 in the Node download was replaced with a $(dpkg --print-architecture)
?
Why did you have this line in your dockerfile?
npm set --global registry https://repo.pnet.ch/artifactory/api/npm/npm/ \
@Roemer would it work for M1 macs / ARM based dev environments if the AMD64 in the Node download was replaced with a
$(dpkg --print-architecture)
?
I changed to the installer script from node, I suppose that this should handle that.
This PR has not had any activity in 180 days. If no activity is detected in the next 14 days, this PR will be closed.
Would Cypress Docker images fulfil the needs? They are available for Linux/amd64
and Linux/arm64
.