-
Notifications
You must be signed in to change notification settings - Fork 95
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
Doesn't work with https for webpack-dev-server #170
Comments
Change |
Piggybacking on this thread. Does that mean @rajzik that if I have two servers...
If I do this I get...
My server starts at |
@rodoabad If you have some sort of routing inside of your application and you get redirected from
There might be problem with timing of your servers. |
I can confirm this works for me:
@praneetha-ck-robo , can you try this and tell if it works? |
@rodoabad you can try to isolate what is causing the error. Try each command separately:
this is step 1, to validate the problem is actually in If your server runs on |
I'm also having this problem with CRA (react-scripts v3.4.3). The way my HTTPS is set is in my
I've tried the answer you suggested @goldylucks, however it seems that when the Webpack server starts it hijacks / overrides the rest of the script. My workaround was to execute this script:
|
Just chipping in to add that I was trying to run end-to-end tests on my Create React App on localhost with https enabled. Initially the server would start but then the test would not get triggered, but by adding the command |
Thank you for taking time to open a new issue. Please answer a few questions to help us fix it faster. You can delete text that is irrelevant to the issue.
Is this a bug report or a feature request?
Version
"start-server-and-test": "^1.9.0"
"cypress": "^3.2.0",
Platform
macOs High Sierra - Version 10.13.6
I am using create-react-app and I am running my development webpack server in https.
So running
npm run cypress:open
, I would expectOnly the first step happens, cypress launcher is not opening up.
This is my scripts config in package.json.
I am facing this issue only for https, not http.
The text was updated successfully, but these errors were encountered: