We will talk through the work Express is doing to grow it's community, focusing on the Triage team and other proposals Express has in the works to grow.
All project committers meet to get to meet each other and talk about current and future initiatives on WebdriverIO. Goal of the session is to get to hang out and talk about testing.
An open discussion of where we are in terms of promises debugging and how are things progressing. Potentially share some information about async iterator usage and how that's working out.
Do we want to include AbortController in core? Does that mean we also have to include EventTarget? How should core handle cancellation? What should the user stories be?
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 a while 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.
This collaboration session will likely focus on issues of concern to current & prospective contributors, but we're also happy to talk with users. We can also talk about how to start contributing and have Q&A if time allows.
I would like to discuss the material I've ended up publishing on MDN about client-side tooling and JS frameworks, especially seen as last year's JS collab summit was such a significant event in terms of helping me research it.
For those who have already looked over the material, I'd like to spend some time getting their thoughts on it. For others, I'd like to solicit feedback on how they think it could be improved. I'll have a questionnaire by then that I can circulate.
In the second half of the session, I'd like to talk a bit about JS beyond the browser — is it appropriate for coverage on MDN, and if so, in what way?
Get up to date with Internationalization and Globalization support for Node.js!
The format of this session will be divided into 3 parts:
A brief overview of the history of Globalization's evolution as achieved through projects of the Unicode Consortium (Unicode, ICU, CLDR), from its beginnings on through to exciting new developments like ICU4X. This will also cover how this work has enabled localization initiatives like i18n in node, and what the new relationship between the OpenJS Foundation and the Unicode Consortium means for projects like ICU, CLDR, and their scaling role within the JavaScript ecosystem.
A discussion on the current status of the i18n initiative in node.
A call for participation in the i18n WG: to support both Globalization in node core, and the localization of node's resources (websites, documentation, etc).
npm has been holding virtual open rfc meetings in order to better communicate with the broader community and this collaboration session is an opportunity to discuss some of the ongoing topics with active members of the summit while also onboarding new folks that want to participate in the development of the npm cli.
