OpenJS Foundation / OpenJS World 2021 - Development

Application Modernization with Camel JavaScript and OpenShift - Ip Sam & Wuxin Zeng, Red Hat

Apache Camel has been used widely for messaging queue integration and notification. The light way and simple Camel coding structure make it a good choice for developers. The Camel technology is used widely during application modernization. Camel also integrates very well with OpenShift forthe CI / CD pipeline and the deployment process. In this presentation, we will go over the architecture of Camel, and how Camel can be used with JavaScript and deployed to OpenShift. We will walk through a few example of application modernization and review the performance gain using Camel Javascript with OpenShift.

Join the speaker for live Q&A on Slack: Wednesday, June 2 from 16:20 - 16:40 PDT / 01:20 - 01:40 CEST, channel - #openjs_world-development

Building Modern Native Add-ons for Node.js in 2021 - Kevin Eady, Hive Streaming & Gabriel Schulhof

Quickly get up to speed developing modern Node.js native addons. This fast-paced talk, presented by members of the Node-API team for all native add-on developers, covers recent enhancements to Node-API. Support for multi-threaded and asynchronous programming in Node-API has been significantly improved. New abstractions such as thread-safe functions and the Addon class greatly simplify the effort needed to implement asynchronous add-ons. New helper methods support date objects, BigInts, retrieving object property names, and detaching ArrayBuffers. Tools used to build and deploy native add-ons also continue to improve. Developers can build with CMake.js in addition to node-gyp. Prebuilding binaries significantly improves the experience of native add-on users. Deployment options permit serving these binaries from GitHub releases or bundling the binaries in the npm module itself.

Join the speaker for live Q&A on Slack: Thursday, June 3 from 12:00 - 12:20 PDT / 21:00 - 21:20 CEST, channel - #openjs_world-development

Crafting Bespoke PWA Experiences with Angular - Mark Thompson, Google

Progressive Web Applications (PWA) help teams to deliver on the promise of multi-modal, code re-suing solutions for web apps. This is an important moment in time as their usefulness is becoming more visible and the technology as a solution more viable. Angular has first class support PWAs allowing teams to create bespoke progressive web applications experiences that delight users. In our time together, we’ll explore some of the best techniques to make your Angular web app into a dynamic PWA that delivers constant value to your users across platforms.

Join the speaker for live Q&A on Slack, channel - #openjs_world-development
Thursday, June 3 from 06:00 - 06:20 PDT / 15:00 - 15:20 CEST
Thursday, June 3 from 06:20 - 06:40 PDT / 15:20 - 15:40 CEST

Capacitor is an open source runtime for building Web Native apps backed by the Ionic Framework team allowing you to take your JavaScript app and submerge it into the exciting world of platform api’s and devices for diverse developments. NativeScript is an open source technology empowering JavaScript developers with access to native platform api’s. The marriage of Capacitor and NativeScript provides some exciting capabilities for enriched development experiences and end user satisfaction. Let’s take a look together at how we can make Capacitor “flux” at 88 mph with NativeScript for far reaching JavaScript applications.

While there are established debugging techniques for well known problem types, we have come across rare and complex yet interesting production issues - stemming from pervasive build, deployment configurations and heterogeneous workload types that node.js is subjected to. In this session, we will illustrate case studies of few unique issues that we debugged, custom diagnostic tools that were used and lessons learned. The attendees will learn addressing deeper level production problems and self-diagnose anomalies.

Node.js: The New and the Experimental - Bethany Griggs, Red Hat
Node.js core does not have an official roadmap - it’s the sum of the interests and efforts of the contributors that determine the future of the project. The evolution of a new feature in Node.js can take different twists and turns. Some new features land as experimental, to give time to gather user feedback before they’re considered stable. Other features will land as stable from the start. So what’s in the pipeline?

Join the speaker for live Q&A on Slack: Thursday, June 3 from 02:20 - 02:40 PDT / 11:20 - 11:40 CEST, channel - #openjs_world-development

Shiver My Timbers! Migrating yargs to ECMAScript Modules - Benjamin Coe, Google

The ECMAScript Modules standard has existed for 11 years, but it was only in April 2020 that the Node.js implementation was marked stable. Up until this point, it was difficult for the npm community to truly adopt modules, given the importance of Node.js to JavaScript tooling. Stability declared, library authors can now start thinking about a future that includes modules. ECMAScript Modules create exciting possibilities for library authors: it's now possible to target multiple JavaScript platforms, such as Deno, Node.js, and the modern web; modules have a separate loading step, making it possible to perform optimizations like tree shaking; and, they're standards backed. In this talk, Ben provides a recipe for releasing libraries that support both CommonJS (require statements) and ECMAScript modules (import and export statements), based on their experience migrating the library yargs.

Join the speaker for live Q&A on Slack: Thursday, June 3 from 11:00 - 11:20 PDT / 20:00 - 20:20 CEST, channel - #openjs_world-development

Your user closes the browser tab and your excellent frontend app immediately disappears. But what if you want to build even better UX by keeping a portion of your app always alive - to send & receive events, to finish network operations, and to run some code even when a user does not have your website open? During my session, let's explore all the possibilities we have in the Service Worker-driven APIs to create true Phantoms of our apps. All for good: to keep the app itself and content always fresh, network operations - resilient, and user - notified

When building with GraphQL you define the schema up front and this can be really handy go use when it comes to writing the queries, resolvers, etc., especially if it’s in TypeScript. So, how do you go about doing the type generation? We’ll take a look at a tool that can generate you the TypeScript types, then implement our backend using them before looking at how they can plug into the front end with React Hooks. We’ll cap off by learning how to model our storage platform effectively using its own types and combine them with the GraphQL schema types.

Upgrading to Fastify 3 - Austin Akers, Microsoft

The lessons learned upgrading our codebase from Fastify 2.x to 3.x and how to mitigate migration headaches.

Join the speaker for live Q&A on Slack, channel - #openjs_world-development
Wednesday, June 2 from 14:20 - 14:40 PDT / 23:20 - 23:40 CEST
Thursday, June 3 from 13:00 - 13:20 PDT / 22:00 - 22:20 CEST

We live in a world of applications. There’s a constant tug-of-war between wanting to maintain only one source code versus our app having a home everywhere our users are found. With Angular, we can write web apps that run great on both desktops and on mobile. When combined with NativeScript, we can take the next step and run our JavaScript natively on mobile devices. We’ll look at how to create both a web app and a native iOS and Android application from one codebase, sharing our code between the web and native. Together we can forge our apps using the power of Angular and Nativescript and finally have one source to rule them all. One Source to rule them all, One Source to find them, One Source to bring them all and in the Nativescript bind them.