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
It seems like the development server run with the e2e:open script for Cypress is not running in development mode. While I think it would be useful to be able to run NODE_ENV=production yarn e2e:open for this behavior, I think the default should be development mode.
My reasoning is that I don't think the primary purpose of Cypress' GUI is to get insight into a problem that only happens in the production build, but rather as a development environment for TDD. For that more common use case, it's difficult to troubleshoot failing tests without dev features like detailed warnings from Vue.
What does the proposed API look like?
My proposal is just changing that script to run the dev server in development mode, switching to production mode only with NODE_ENV=production.
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
It seems like the development server run with the
e2e:open
script for Cypress is not running in development mode. While I think it would be useful to be able to runNODE_ENV=production yarn e2e:open
for this behavior, I think the default should be development mode.My reasoning is that I don't think the primary purpose of Cypress' GUI is to get insight into a problem that only happens in the production build, but rather as a development environment for TDD. For that more common use case, it's difficult to troubleshoot failing tests without dev features like detailed warnings from Vue.
What does the proposed API look like?
My proposal is just changing that script to run the dev server in development mode, switching to production mode only with
NODE_ENV=production
.The text was updated successfully, but these errors were encountered: