Node Interactive North America 2017

Until now, native module (add-ons) maintainers have had to recompile for each Node.js release as well as potentially updating their code to cope with the rapid pace of changes in the v8 APIs. The community API working group has been developing the N-API (Node-API) as a follow on to Nan to help solve this problem and insulate modules from changes in the v8 APIs.

By targeting the new API, modules will be able support a wide variety of Node.js releases without needing recompilation or abstraction layers such as Nan - reducing deployment time and maintenance effort for both module developers and Node.js end users.

With an initial version of the API slated to be part of Node version 8 as an experimental feature, it is a good time to come learn about the shape and usage of the new API from those working to implement it.

You've heard Node.js is single threaded. It's true that all JavaScript executed by Node.js is run in a single thread, but JS isn't all. The event loop, written in C++, is multi-threaded! Come learn how the event loop works, how it affects performance, and how you can use it your advantage!

This talk is about creating Node.js interfaces for native libraries written in C or C++. It starts talking about various situations in which you need to build native addons and the common problems in doing that.
I'll discuss about the portion of the node.js documentation that describes native addons, the api fragmentation, and the reference provided by the Native Abstractions.
With all these tools and knowledge i'll show you how to build some addons from scratch and explain how to keep your code asynchronous.
Along the practical examples i will illustrate the best practice to follow in building native addon and give you some statistics about the performance improvements for the app that use native addons.
At the end i will show what will be the future developments will like and talk about new N-API.

This panel discussion will feature module and ecosystem developers who will be asked to discuss the top things that Node.js Core developers should know about the ecosystem. What are their priorities? What makes their lives more difficult? What should core be doing better? What should we not be doing at all?

The build workgroup (https://github.com/nodejs/build/) has the mission to provide Node.js Foundation projects with solid computing infrastructure covering a wide range of platforms and different software stacks. In this talk we will introduce the general philosophy of how infrastructure is sourced, which has a strong focus on community donations, the overall picture of the substantial infrastructure we've managed to build using this approach, some of the interesting interactions and, just as important, how you might get involved. Come learn about the infrastructure that powers the delivery of Node.js!

ES Modules and Common JS go together like old bay seasoning and vanilla ice cream.

This talk will dig into the inconsistencies of the two patterns, and how the Node.js project is dealing with reconciling the problem. The talk will look at the history of modules in the js ecosystem and the subtle difference between them. It will also skim over how ecma-262 is standardized by the tc39, and how esmodules were developed.