Skip to content

N-API 6 #393

Description

@gabrielschulhof

The only outstanding backport for new N-APIs is nodejs/node#31384 which brings napi_get_all_property_names to v10.x. Shall we wait until it lands to make off N-API 6 as including napi_get_all_property_names, or shall we leave napi_get_all_property_names experimental and roll N-API 6 without it?

Once we have arrived at a decision, we need to file a PR in core that bumps the NAPI_VERSION and updates the preprocessor if-block into which the N-API declarations are placed.

Activity

  1. legendecas commented on Mar 2, 2020

    @legendecas
    Member

    Since nodejs/node#31384 has landed on v10.x-staging as nodejs/node#31384 (comment), I'd believe we're going to roll N-API 6 with napi_get_all_property_names if there are no other issues arisen.

  2. mhdawson commented on Mar 2, 2020

    @mhdawson
    Member

    @gabrielschulhof looks like we are ready to go

  3. gabrielschulhof commented on Mar 2, 2020

    @gabrielschulhof
    CollaboratorAuthor

    Excellent!

  4. added a commit that references this issue on Mar 9, 2020
  5. added a commit that references this issue on Apr 2, 2020
  6. added a commit that references this issue on Apr 6, 2020
  7. added a commit that references this issue on Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions