New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global mode documentation #427

RandallKent opened this Issue Mar 1, 2018 · 4 comments


5 participants

RandallKent commented Mar 1, 2018

While we currently recommend installing Cypress via npm, the direct download (global mode) shouldn't be treated as a second-class citizen. As such, we need some documentation on working with global mode

  • How global mode is different
  • Tradeoffs when using global mode (e.g. cypress-io/cypress#1131)
  • When to use global mode
  • How to tell if you're running global mode
  • Adding projects
  • Removing projects
  • Upgrading global mode installation

This comment has been minimized.


brian-mann commented Apr 12, 2018

Yeah so when you setup a project to record on the dashboard - when we give you the "success" message we need to instead of saying cypress run in the terminal provide you a message to the docs that says: hey you need to install the npm module!!

@Bkucera Bkucera removed their assignment Jun 6, 2018


This comment has been minimized.


jennifer-shehane commented Aug 1, 2018

I think it'd be a good idea to put in a note in the "Direct Download" section that Cypress won't run headless if you download directly and try to run the binary.


This comment has been minimized.


jennifer-shehane commented Oct 4, 2018


@jennifer-shehane jennifer-shehane self-assigned this Oct 4, 2018


This comment has been minimized.

ViggoV commented Nov 15, 2018

Is there a global mode?! I was about to completely write off Cypress as I try to keep my projects as clean as possible and the installer was downloading binaries and creating tons of sample files inside my project. I've literally been googling 'cypress global install' for hours and all I found until I combed the Issues page was an earlier, closed issue with someone who couldn't get it to work.

So in other words: +1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment