Skip to content

url.parse is deprecated #16

@ShenHongFei

Description

@ShenHongFei

nodejs/node#55017

(node:33948) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
    at urlParse (node:url:129:13)
    at fastparse (webpack://my-repl/node_modules/.pnpm/parseurl@1.3.3/node_modules/parseurl/index.js:97:1)
    at parseurl (webpack://my-repl/node_modules/.pnpm/parseurl@1.3.3/node_modules/parseurl/index.js:51:1)
    at Object.get path (webpack://my-repl/node_modules/.pnpm/koa@2.15.3_patch_hash=p7ybv54qzz4vmboaajk6ep5psi/node_modules/koa/lib/request.js:145:1)
    at Object.router (D:\0\lib\server.ts:763:66)
    at dispatch (webpack://my-repl/node_modules/.pnpm/koa-compose@4.1.0/node_modules/koa-compose/index.js:42:1)
    at cors (webpack://my-repl/node_modules/.pnpm/@koa+cors@5.0.0/node_modules/@koa/cors/index.js:109:1)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async compressMiddleware (webpack://my-repl/node_modules/.pnpm/koa-compress@5.1.1/node_modules/koa-compress/lib/index.js:56:1)
    at async Object.entry (D:\0\lib\server.ts:724:13)

Can it be achieved by other alternative methods?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions