refactor: replace legacy url API #113
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
描述
将旧的URL API替换为WHATWG URL API
原因
根据Nodejs.org上的文档，旧的URL API在Node.js v11.0.0版本被弃用，直到v15.13.0才被撤销弃用，改为Legacy。[1]
我Windows上的VS Code版本号为v1.55.0，其Node.js版本号为v12.18.3；
我Deepin v20.1上的VS Code版本号为v.1.51.0，其Node.js版本号为v12.14.1，均适用本次修改。
新的问题
URL类不支持直接解析纯相对路径(即只提供“/song/:id")，我在runtime.js中只做了临时处理。😅
是不是要先开个issue讨论？😀