fix: prevent Invalid URL error in prepareBaseUrl for http/https baseUrl #8434
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes an
Invalid URL
error that occurs when usingbaseUrl
withhttp
orhttps
values in TestCafe 3.7.1+ on Node.js 20.18+.Current behavior
The current implementation of
prepareBaseUrl
appliespath.join
to the providedbaseUrl
.For web URLs, this produces invalid results:
new URL("http:/devexpress.github.io/")
→ throwsTypeError: Invalid URL
This breaks
.page(...)
and config-basedbaseUrl
when using standard web URLs.Expected behavior
baseUrl
is always treated as a web URL if it starts withhttp://
orhttps://
.file://
.How does this PR fix the problem?
http://
andhttps://
URLs (adds trailing slash if missing).file://
URLs.pathToFileURL
.Related issue
Fixes #8364