-
Notifications
You must be signed in to change notification settings - Fork 97
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
Node 17 support #333
Comments
bump |
It's been awhile since we saw an update for this repository so it might take awhile. |
I'm seeing the same issue with node 16, but I'm not with node 14. but instead of Cypress, I see it with serverless-offline edit: Ok false alarm. The problem was not this package. It turns out the base url for |
Node 16 should work. 17+ does not. |
This might be related to this issue (of the underlying |
What we did was actually the opposite (people can either do it one way or another). We had a server that was starting at |
It worked for me with 127.0.0.1 |
Can confirm it does not work for |
* Update ci.yml * Updated code formatting and fixed CI (#221) * Updated code formatting * Delete package-lock.json * Fixed CI issue and updated dep version * Updated netlify build env * added --expect 200 * Added fix for Node17+, bahmutov/start-server-and-test#333
@bahmutov is there any plan to fix this issues? Many tools are now using Node 18 as the default version since we are only 6 months away from having no support on Node 16. |
Yes I will look into this |
Can someone provide a reproducible example? I have tested this tool using Node v18 in #354 and don't see any problems. |
In my project only Mac users have issues, not Linux users. |
🎉 This issue has been resolved in version 1.15.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@bahmutov I just tested with version 2 and I got the issue happening again. I suspect there is another issue to fix. It's only happening on this script: "e2e-build-headless-base-path": "cross-env CYPRESS_isProd=true BASE_PATH=/some-path CYPRESS_basePath=/some-path start-server-and-test start-example-build http://localhost:3000/some-path cypress-headless", This one seems to work fine: "e2e-build-headless": "cross-env CYPRESS_isProd=true start-server-and-test start-example-build http://localhost:3000 cypress-headless", Feel free to try to reproduce cloning this repo: https://github.com/Avansai/next-multilingual Can run |
Could you say which OS you are testing on? |
I'm on macOS 13.2.1 Regarding
If you check the script for Of course, you need to be on Node >= v18+. It didn't do this when I was on Node 16. |
Could you please open a new issue and include debugging verbose logs?Sent from my iPhoneOn Feb 27, 2023, at 22:33, Nicolas Bouvrette ***@***.***> wrote:
I'm on macOS 13.2.1
Regarding next-multilingual here would be step-by-step reproductions:
Clone https://github.com/Avansai/next-multilingual
run npm run install
run npm run build
Open package.json and make sure that all the 127.0.0.1 are replaced by localhost
run npm run test
If you check the script for npm run test you will see that there are 4 different subscripts being run with different start-server-and-test steps. The 3rd step will hang, and when I press ctrl-c it sort of resumes but go back into the same stuck step.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Sure. How do I turn on verbose logs? |
Check out the debugging section of the readme. Just need to set DEBUG env variable when running with the name of the module Sent from my iPhoneOn Feb 27, 2023, at 22:59, Nicolas Bouvrette ***@***.***> wrote:
Sure. How do I turn on verbose logs?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I was hoping to be able to try this out, however on https://github.com/actions/runner-images |
Bug report
Hi, as mentioned in #328 by several people, it seems the package doesn't support node 17+ or at least is unable to execute a command after the server is up and ready. I created a new issue in case it is a different topic than #328 (probably is).
start-server-and-test start 8000 cy:open
should start the app server and open CypressThe text was updated successfully, but these errors were encountered: