Skip to content

url.parse() behavior is not standardized and prone to errors that have security implications #24

Description

@mitchdowney

Last I checked, I think this was a known issue with Next 16, and I was waiting for a fix from Next.

▲ Next.js 16.1.6
- Local:         http://podverse-web-6476dfdfb6-g4h7q:3000
- Network:       http://podverse-web-6476dfdfb6-g4h7q:3000
✓ Starting...
✓ Ready in 119ms
(node:1) [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.
(Use `node --trace-deprecation ...` to show where the warning was created)

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions