Skip to content

doc: Different information about when functions have been "Added" are confusing #40037

@Tilogorn

Description

@Tilogorn

📗 API Reference Docs Problem

  • Version: -
  • Platform: -
  • Subsystem: crypto

Location

Section of the site where the content exists

Affected URL(s):

Description

Concise explanation of the problem

The node version a function has been added to changes according to what release API docs you are looking at. I observed this with crypto.randomUUID().

I understand that this may be due to branching. I guess v15.6.0 had it first, and v14.17.0 became it as an LTS update. But when I look up a function and see in the current docs (which are often the first hit in search engines) that it is available since v15.6.0 and I know my code is using v14.x I automatically assume I am not able to use this feature. Which is wrong in this case because it has already been added in v14.17.0 ("already" not necessarily as in "earlier in time" but as in "a lower version number").

This may be a conceptual decision and as soon as I know it, I am aware of it. But maybe it happened by accident and this issue might help improving the docs.


  • I would like to work on this issue and
    submit a pull request.

Metadata

Metadata

Assignees

No one assigned

    Labels

    docIssues and PRs related to the documentations.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions