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 happens due to this change in Node.js: nodejs/node#40537. We will try to fix it ASAP. Right now, you can add this line at the start of some of your test files or a JS config file:
What is your Scenario?
Everything works fine on Node 14.
Update to Node 18 leads to "500 Internal Server Error" while loading
http://localhost:5003/GFxi51qUa!s!utf-8/http://localhost:8080/hub/assets/main.js
though http://localhost:8080/hub/assets/main.js is available
Checked the same problem with different domain names (besides localhost).
See attached screenshots.
What is the Current behavior?
It seems there is some internal problem with testcafe proxying, should work correctly
What is the Expected behavior?
Should work correctly
What is your public website URL? (or attach your complete example)
What is your TestCafe test code?
Standard site using webpack-devserver
Your complete configuration file
No response
Your complete test report
No response
Screenshots
Steps to Reproduce
TestCafe version
2.1.0
Node.js version
18.12.1
Command-line arguments
Browser name(s) and version(s)
Chrome 107.0.5304.122
Platform(s) and version(s)
Windows
Other
No response
The text was updated successfully, but these errors were encountered: