Can't run Cypress Open
up vote
0
down vote
favorite
I recently took over a cypress project; running on windows. The first time I installed, all was working. Now, subsequent to upgrading node/electron/chrome, I can't open cypress with any command. Here's what I tried:
- Delete node_modules directory in my project.
npm initAnswered with all defaults. node_modules directory is present but empty.
npm install cypress --save-dev(from [the doc][1]). This populated my node_modules, but installed cypress in my account (users) directory.
node_modules.bincypress openThat reported:
- It looks like this is your first time using Cypress: 3.1.1
- Verified Cypress: [in my users dir]
- Opening Cypress...
At that point I can see cypress in my process list, but the UI never shows. I can run headless tests normally, so I'm OK from a CI perspective, but I still want to open the UI with my tests locally. I can launch the cypress executable in my user dir and then open my project root directory manually, but can't run an open command normally. The scripts section of package.json doesn't seem to be designed to accept a path to an exe with params.
Is there another way to call open that I'm missing?
cypress
asked Nov 12 at 20:22
dudeNumber4
1,39312040
add a comment |
up vote
0
down vote
favorite
I recently took over a cypress project; running on windows. The first time I installed, all was working. Now, subsequent to upgrading node/electron/chrome, I can't open cypress with any command. Here's what I tried:
- Delete node_modules directory in my project.
npm initAnswered with all defaults. node_modules directory is present but empty.
npm install cypress --save-dev(from [the doc][1]). This populated my node_modules, but installed cypress in my account (users) directory.
node_modules.bincypress openThat reported:
- It looks like this is your first time using Cypress: 3.1.1
- Verified Cypress: [in my users dir]
- Opening Cypress...
At that point I can see cypress in my process list, but the UI never shows. I can run headless tests normally, so I'm OK from a CI perspective, but I still want to open the UI with my tests locally. I can launch the cypress executable in my user dir and then open my project root directory manually, but can't run an open command normally. The scripts section of package.json doesn't seem to be designed to accept a path to an exe with params.
Is there another way to call open that I'm missing?
cypress
asked Nov 12 at 20:22
dudeNumber4
1,39312040
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I recently took over a cypress project; running on windows. The first time I installed, all was working. Now, subsequent to upgrading node/electron/chrome, I can't open cypress with any command. Here's what I tried:
- Delete node_modules directory in my project.
npm initAnswered with all defaults. node_modules directory is present but empty.
npm install cypress --save-dev(from [the doc][1]). This populated my node_modules, but installed cypress in my account (users) directory.
node_modules.bincypress openThat reported:
- It looks like this is your first time using Cypress: 3.1.1
- Verified Cypress: [in my users dir]
- Opening Cypress...
At that point I can see cypress in my process list, but the UI never shows. I can run headless tests normally, so I'm OK from a CI perspective, but I still want to open the UI with my tests locally. I can launch the cypress executable in my user dir and then open my project root directory manually, but can't run an open command normally. The scripts section of package.json doesn't seem to be designed to accept a path to an exe with params.
Is there another way to call open that I'm missing?
cypress
asked Nov 12 at 20:22
dudeNumber4
1,39312040
I recently took over a cypress project; running on windows. The first time I installed, all was working. Now, subsequent to upgrading node/electron/chrome, I can't open cypress with any command. Here's what I tried:
- Delete node_modules directory in my project.
npm initAnswered with all defaults. node_modules directory is present but empty.
npm install cypress --save-dev(from [the doc][1]). This populated my node_modules, but installed cypress in my account (users) directory.
node_modules.bincypress openThat reported:
- It looks like this is your first time using Cypress: 3.1.1
- Verified Cypress: [in my users dir]
- Opening Cypress...
At that point I can see cypress in my process list, but the UI never shows. I can run headless tests normally, so I'm OK from a CI perspective, but I still want to open the UI with my tests locally. I can launch the cypress executable in my user dir and then open my project root directory manually, but can't run an open command normally. The scripts section of package.json doesn't seem to be designed to accept a path to an exe with params.
Is there another way to call open that I'm missing?
cypress
cypress
asked Nov 12 at 20:22
dudeNumber4
1,39312040
asked Nov 12 at 20:22
dudeNumber4
1,39312040
edited Nov 12 at 21:28
asked Nov 12 at 20:22
dudeNumber4
1,39312040
asked Nov 12 at 20:22
dudeNumber4
1,39312040
asked Nov 12 at 20:22
dudeNumber4
1,39312040
1,39312040
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Did you upgrade the Electron version that Cypress uses? Cypress uses Electron 1.8.2 which is significantly behind the latest, and Cypress does not currently support newer versions of electron. See this Github issue for more info.
answered Nov 15 at 15:26
Joshua Wade
795316
Yes. Guess that's the problem, though it's strange I can launch it directly and it works just fine.
– dudeNumber4
Nov 16 at 16:15
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53269535%2fcant-run-cypress-open%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Did you upgrade the Electron version that Cypress uses? Cypress uses Electron 1.8.2 which is significantly behind the latest, and Cypress does not currently support newer versions of electron. See this Github issue for more info.
answered Nov 15 at 15:26
Joshua Wade
795316
Yes. Guess that's the problem, though it's strange I can launch it directly and it works just fine.
– dudeNumber4
Nov 16 at 16:15
add a comment |
up vote
0
down vote
accepted
Did you upgrade the Electron version that Cypress uses? Cypress uses Electron 1.8.2 which is significantly behind the latest, and Cypress does not currently support newer versions of electron. See this Github issue for more info.
answered Nov 15 at 15:26
Joshua Wade
795316
Yes. Guess that's the problem, though it's strange I can launch it directly and it works just fine.
– dudeNumber4
Nov 16 at 16:15
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Did you upgrade the Electron version that Cypress uses? Cypress uses Electron 1.8.2 which is significantly behind the latest, and Cypress does not currently support newer versions of electron. See this Github issue for more info.
answered Nov 15 at 15:26
Joshua Wade
795316
Did you upgrade the Electron version that Cypress uses? Cypress uses Electron 1.8.2 which is significantly behind the latest, and Cypress does not currently support newer versions of electron. See this Github issue for more info.
answered Nov 15 at 15:26
Joshua Wade
795316
answered Nov 15 at 15:26
Joshua Wade
795316
answered Nov 15 at 15:26
Joshua Wade
795316
answered Nov 15 at 15:26
Joshua Wade
795316
795316
Yes. Guess that's the problem, though it's strange I can launch it directly and it works just fine.
– dudeNumber4
Nov 16 at 16:15
add a comment |
Yes. Guess that's the problem, though it's strange I can launch it directly and it works just fine.
– dudeNumber4
Nov 16 at 16:15
Yes. Guess that's the problem, though it's strange I can launch it directly and it works just fine.
– dudeNumber4
Nov 16 at 16:15
Yes. Guess that's the problem, though it's strange I can launch it directly and it works just fine.
– dudeNumber4
Nov 16 at 16:15
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53269535%2fcant-run-cypress-open%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
