Session Proposal: Unifying hook systems in Node.js #294
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
Proposal
Topic of the session
Unifying the disparate efforts around building hook systems into Node.js
Type of the session
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
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
The text was updated successfully, but these errors were encountered: