Skip to content

Bug: False positive for canParse in n/no-unsupported-features/node-builtins #243

Closed
@rasmuslp

Description

@rasmuslp

Environment

Node version: 20.11.0
npm version: 10.2.4
ESLint version: 8.57.0
eslint-plugin-n version: 17.2.0
Operating System: macOS Sonoma 14.4.1

What rule do you want to report?

n/no-unsupported-features/node-builtins

Link to Minimal Reproducible Example

https://eslint-online-playground.netlify.app/#eNp1kcFOAyEQhl9lw0mTdtd4XFNPHk00Rr1ID5Sdtugy4ACmTdN3dwBrWk3DBWb++eYfZicC6Q42yvoR2vcgemGsdxSbRGOzJGcbKdAN0PNbihuJErXDEJs1wbKZcXYdow99161MXKdFq53tIIwG45SvNqGJ20PAj2llcIoF1EhkZvvydN9qhY+KAlxk6KWYiLYWkGZLDtnUjvXcCzYRcAhS9M0bv4qoJ8iNOA6DFBNW1TY9dieZ+aQyfO5EDz4aniOTCrvQtVWvQIETOS7FqCKEyNCDIrhEGp63HqrAuiGNfM/5/Q+fOHLK/UyOOQfTRI6qz8GlRa6el3KJe57cK/2hVnkVx3MP8HUHPg+C2vyh1184Y/jfxx+rjl0DsuCXLCOfsvdacTu7vsp6GYvN/TdBo75l

What did you expect to happen?

Rule reports that URL.canParse is still an experimental feature, and I don't believe that is correct.

According to Node documentation [1] this API was added in 19.9.0, but there is no mention of it being experimental.

[1] https://nodejs.org/docs/latest-v20.x/api/url.html#urlcanparseinput-base

Participation

  • I am willing to submit a pull request for this issue.

Additional comments

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions