Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session Proposal: Unifying hook systems in Node.js #294

Closed
3 of 11 tasks
Qard opened this issue Jun 2, 2020 · 5 comments
Closed
3 of 11 tasks

Session Proposal: Unifying hook systems in Node.js #294

Qard opened this issue Jun 2, 2020 · 5 comments
Assignees
Labels
Austin 2020 Collaborator Summit Project Working Session Track for proposals that support a specific project's needs Session Proposal A session proposal for the Collaboration Summit

Comments

@Qard
Copy link

Qard commented Jun 2, 2020

Proposal

Topic of the session

Unifying the disparate efforts around building hook systems into Node.js

Type of the session

  • Collaborate
  • Workshop
  • Talk

Timezone of facilitator

UTC-8, but I'm available basically any time.

Estimated duration of the session

1-2 hours

Follow-up / Set-up sessions (if any)

#273 and #293 are likely to be relevant.

Level

  • Beginner
  • Intermediate
  • Advanced

Pre-requisite knowledge

Awareness of any hook systems would be helpful

Describe the session

Over the years the number of needs emerging for hooking into the API call lifecycle has increased. There are many parallel efforts that could use some unified vision to ensure we come to the most flexible yet performant solution we can.

We've had async_hooks for awhile now, providing an identifying hook into the async stack graph. There was also discussion about a generic diagnostics channel for APIs to communicate diagnostic data to any interested consumers such as APMs. More recently, we've seen efforts around policy enforcement, es module loader hooks, input validation or modification, and mocking.

I would like to discuss what the numerous needs are for a hook system in Node.js, where needs intersect, and chart a path forward to implement something that can satisfy those needs as effectively and as efficiently as possible.

Session facilitator(s), Github handle(s) and timezone(s)

Stephen Belanger (@Qard) - PST

Additional context (optional)

Any exposure to any existing or prior hook-related efforts is helpful, including:


This section is for contributors handling Collaborator Summit logistics

Track

Triage

  • Track chosen
  • Scheduled
@vdeturckheim
Copy link

Huge +1 on this.

@jorydotcom jorydotcom added the Project Working Session Track for proposals that support a specific project's needs label Jun 5, 2020
@Qard
Copy link
Author

Qard commented Jun 26, 2020

If anyone is interested in continuing the discussion, I'm arranging another meeting here: nodejs/diagnostics#401

@jorydotcom
Copy link
Collaborator

Notes from the session

@Qard do you know if this session was recorded?

@Qard
Copy link
Author

Qard commented Jul 3, 2020

Hmm...I don’t think it was, unfortunately.

@WaleedAshraf
Copy link
Member

Closing this issue as no further action is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Austin 2020 Collaborator Summit Project Working Session Track for proposals that support a specific project's needs Session Proposal A session proposal for the Collaboration Summit
Projects
None yet
Development

No branches or pull requests

6 participants