Apply Cypress Dependencies

This is meant to only have to install 1 depndencies to get Cypress up and running and then keeping this up to date with latest version and re-versioning this NPM package to keep the other installations clean and up to latest WORKING versions of dependencies.

Workflow

1. Test new versions out on E2E-mainhub and test the new versions out
2. Update apply-cypress-dependencies
3. Update projects

New version fails

1. Pull back to previous version
2. Re-create the problem in E2E-mainhub
3. See if you can fix it or find another version combo that works
4. Update this repo with a new version.

Versioning

Follow the same version that Cypress is at. If we are using Cypress 6.5.0, then this version (changed in package.json) should be 6.5.0. To make it easier connet them both.

If you run into a problem that you need to change a dependency thats not Cypress, increase Cypress version by 1.

Example: 7.0.2 would become 7.0.3

Publishing

!NOTE! Always need to increase the version by at least 0.0.1 to be able to publish your changes!

All tokens and passwords can be accessed in 1Password under Apply-cypress-dependencies

1. Create a side branch
2. Make your changes
3. Create a merge request
4. When approved, merge into main
5. Run npm login. username: applydigital, password <in 1Password>, email: [email protected]
6. Before publishing, you need to run: export NPM_TOKEN=<in 1Password>
7. To publish: npm publish --access public
8. New version has been published.

Token issue

If you are first to install these dependencies in a project that is accessing Apply's NPM with a hiden/private repo, then you will run into issue where you need to run:

export NPM_TOKEN=tokenStuff