Get rid of deprecated Node.js API: url.parse · huan/file-box#20

(0 comments) (0 reactions) (0 assignees)TypeScript (58 stars) (9 forks)user submission

bughelp wanted

説明

https://github.com/huan/file-box/blob/3788e591fad15a2ec00868a3150d1e136e3898dc/src/misc.ts#L90-L98

If we use new url.URL() to replace url.parse, the unit tests will fail, and the reason still needs to be found.

`url.parse`

Url {
  protocol: 'https:',
  slashes: true,
  auth: null,
  host: 'httpbin.org',
  port: null,
  hostname: 'httpbin.org',
  hash: null,
  search: null,
  query: null,
  pathname: '/headers',
  path: '/headers',
  href: 'https://httpbin.org/headers' }

`new url.URL`

URL {
  href: 'https://httpbin.org/headers',
  origin: 'https://httpbin.org',
  protocol: 'https:',
  username: '',
  password: '',
  host: 'httpbin.org',
  hostname: 'httpbin.org',
  port: '',
  pathname: '/headers',
  search: '',
  searchParams: URLSearchParams {},
  hash: '' }
https://httpbin.org/headers

コントリビューターガイド

技術スタック: typescriptnodejs
領域: backend
Issue 種別: refactor
難度: 3
推定時間: 1-3 hours
活動状況: stale
明確さ: mostly clear
前提条件: Node.js URL APITypeScript
初心者向け度: 60
調査方針: Examine the file src/misc.ts at lines 90-98 to see the current usage of url.parse. Review the unit tests to understand why they fail when using new url.URL(). The difference in output properties (e.g., auth vs username/password) may affect test assertions. Look for existing test files and consider adapting assertions to match WHATWG URL API output.