A closer look at package management Since there are 100+ highly inter-connected internal npm packages which declare over 2,500 external dependencies, we will briefly take a look at how packages and dependency management. We will discuss the structure of each package in the monorepo and how dependencies are expressed across these packages. The packages contain transpiled TypeScript code and bundles generated using webpack and the modules from these bundles are used across various product endpoints. Handling package dependencies We use yarn workspaces to install our external dependencies and link the Midgard-hosted packages together based on the dependencies expressed in the package.json files. We will use an example with yarn workspaces to handle package dependencies in a sample monorepo. Cross-package orchestration The other major part of managing monorepos is cross-package orchestration. We would want to execute scripts across all the packages easily like build/packaging commands, linting, etc. We will take a look at achieve this using Lerna through the talk. Using Test Apps to validate user behaviour To validate more complex component behaviors, like user interactions, we use test-apps. Test apps are either webpages or native applications which load our bundles to render our components for manual testing. This is probably the second most popular validation workflow, therefore we care a lot about it. Improving “watch” across packages We will also briefly look at how we will manage watch processes for the monorepo-hosted packages. Its also important to discuss the Intellisense performance here. We will go over a sample monorepo structure to explain this in detail.

Codemods - Why and What, Problem with Regex pattern matching, Find & Replace Limitations, AST, How codemods work, Tooling around codemods - jscodeshift, recast, astexplorer.net, ast-types, codemod-cli and possibly a small demo of creating a codemod if time permits.

What to expect? (2 minutes) Background and motivation (5 minutes) Linguistic spread across regions in India Ethnic literature and music Current status of documentation and archives Project Langdon (15 minutes) Inspiration UI development with Semantic/Fomantic UI for React UI development with StorybookJS Testing with Jest User Authentication with AWS Amplify and Amazon Cognito Role based access control with Amazon Cognito Identity Pools Schema development with GraphQL Graph data persistence with Amazon Neptune API design with AWS Lambda functions and API Gateway CI/CD with Travis CI and Surge Next steps (5 minutes) Features Community and developer experience QnA (5 minutes)

Optional Chaining What is it? Usecases Code samples Current Hacks Current Status Integrating with our build tools Null Coalescing What is it? Usecases Code samples Current Hacks Current Status Integrating with our build tools

Break down to take down: The title might seem vague but breaking down the project into meaningful modules is what most of us miss out on. Well, by meaningful I mean not only is it important to break down code base into individual modules but also to make those modules reusable. This session would also summarise my learnings while working on a product that relies heavily on the smooth working of a Javascript Library(which is obviously broken down into modules) and how we manage that. I would also talk about the different module patterns and when to use them. Moreover every Javascript framework depends on a good design system. In short, this session would give a clear picture on how breaking down your codebase will help you take down a lot of problems. I plan to cover the below mentioned points -: Why focus on this? Examples to depict how modular system helps in writing efficient program in less number of lines. Importance of making modules meaningful. Give more power to your modules by writing end-to-end and unit test cases. Different Modular Patterns -: Facade Pattern (pros & cons) Mediator Pattern (pros & cons)

Overview on ARIA Role that ARIA plays when it comes to making custom widgets accessible Demonstrating few examples of accessible custom widgets and how to achieve them using ARIA.

In this talk, we would not be speaking about why GraphQL is great(we know it is great) but rather we would be more focused what were some difficulties we faced while using GraphQL and why we had a call to revert back to REST and remove GraphQL. Introduction Why revert GraphQL? Thumb rules to decide: GraphQL or REST.

Topics Introduction to purescript Differences from other compile to JS languages Types and Functions Functors and Monads JS Interop Web frameworks Summary