Skip to content

N-API 7 #402

Closed
Closed

Description

@gabrielschulhof

Might it be time for a new version of N-API?

We have the buffer detaching stuff marked as experimental in all three LTS releases, so we could just define these APIs as N-API 7.

We also have type-tagging and asynchronous env cleanup coming on master, but those still need to be backported. As v10.x approaches EOL it is increasingly unlikely that they will be backported all the way there. Thus, it might make sense to sync our N-API version bump with the EOL of 10.x.

Shall we formalize and document our policy for moving APIs out of experimental and into a stable version of N-API?

Activity

  1. added this to the Milestone 11 milestone on Aug 3, 2020
  2. mhdawson commented on Aug 17, 2020

    @mhdawson
    Member

    We agreed:

    • that we should make buffer detaching stable in N-API 7
    • that type-tagging and async env cleanp should wait until N-API 8, possibly around the Node.js 16.x release timeline.
  3. gabrielschulhof commented on Sep 16, 2020

    @gabrielschulhof
    CollaboratorAuthor

    @Flarna asked that nodejs/node#35214 be folded into N-API 7 because it's such a small change. Let's discuss at our next meeting.

  4. changed the title [-]Discussion: N-API 7[/-] [+]N-API 7[/+] on Sep 25, 2020
  5. mhdawson commented on Oct 23, 2020

    @mhdawson
    Member

    All ready to go, just waiting next 10.x release and then we can close this.

  6. mhdawson commented on Oct 30, 2020

    @mhdawson
    Member

    Landed in 10.x, done !

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

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions