Santosh Yadav

The default templates provided by React or Next can be a great starting point for most projects, but as soon as your app grows, you may want to customize the workspace to fit your needs. But the question is how to do it; also, what if you want to introduce new tooling to your workspace like Cypress or Playwright? How about keeping your workspace evergreen? It's manual work. The current answer for your team must be a custom script. Adding more tools means increasing your build time. Does it all sound relatable to you? Join me in this talk to see how you can give superpowers to your React/Next or Remix workspace and make your team more productive. Key Takeaways: - Customizing your workspace - Nx generators - Nx Executors - Adding your own tooling

Maintaining a huge codebase is always a challenge, you need to ship features, run the business as usual, and introduce new tools, and it becomes more challenging when you have many teams contributing to the code base. At Celonis we use Angular and Nx for monorepo and ship updates to more than 40+ apps, which have 2 million lines of code, and we are adding more apps and libraries as we go. Nx is a build tool, with the support for mono-repos and provides the flexibility to bring any tools/framework/technology to the mono-repo and helps to reduce build time by providing the ability to cache builds. Maintaining this huge codebase is a challenge, especially when you need to ship updates to them every week. More challenges come with a codebase this big; you may need new tools in your codebase, and new tools are released every week. What if you need to do a Proof of Concept, add a new Angular App, or update a new version of Angular or tooling like Cypress, Playwright, or Jest? But we also get around 100 PRs per day from more than 30 teams contributing to the codebase; for each PR, we need to Run Unit Test, build, Component Test, User Journey test, and lint. A new feature can break your application: how do you plan your release rollback shipping new features with confidence? But it can cause new features/ bug fixes to be rolled back from other apps; feature flags are an answer, but how can it be done in a codebase this big? In this talk, we explore the world of Nx, where we can build, test, and deploy 40+ apps every week with the help of Nx. You will learn about: Maintaining a huge Angular code base CI/CD, GitHub Actions, Merge Queue Release strategy Feature Flags Introducing new tools to the codebase

Maintaining a huge codebase is always a challenge. You need to ship features, run the business as usual, and introduce new tools, and it becomes more challenging when you have many teams contributing to the code base. At Celonis, we use Angular and Nx for monorepo and ship updates to more than 40+ apps, which have 2 million lines of code. We are adding more apps and libraries as we go. Nx is a build tool that supports mono-repos and allows users to bring any tools/framework/technology to the mono-repo. It also helps reduce build time by allowing users to cache builds. Maintaining this huge codebase is a challenge, especially when you must ship updates to them weekly. More challenges come with a codebase this big; you may need new tools in your codebase, and new tools are released every week. What if you need to do a Proof of Concept, add a new Angular App, or update a new version of Angular or tooling like Cypress, Playwright, or Jest? However, we also receive around 100 PRs per day from more than 30 teams contributing to the codebase; for each PR, we need to Run a Unit Test, build, Component Test, User Journey test, and lint. A new feature can break your application. How do you confidently plan your release rollback to ship new features? However, it can also cause new features/ bug fixes to be rolled back from other apps. Feature flags are an answer, but how can they be done in a codebase this big? In this talk, we explore the world of Nx, where we can build, test, and deploy 40+ apps every week with the help of Nx. You will learn about: Maintaining a huge Angular code base CI/CD, GitHub Actions, Merge Queue Release strategy Feature Flags Introducing new tools to the codebase

This is a talk about the JavaScript build tool Vite with our guest, Matias Capeletto, a core team member of Vite. In the show, Matias talks about Vite, including what it is and how to get started with it. He also talks about Vite's history and how it came to be. Some key points from the talk: Vite is a build tool that can be used to build web applications. -Vite is fast. It uses a new architecture that allows it to bundle code very quickly. Vite is easy to use. It has a simple configuration and can be used with most JavaScript frameworks. Vite is under active development. The team behind Vite is constantly adding new features and improving the tool. To get started with Vite, you can create a new project using the Vite CLI. You can also install Vite as a dependency in an existing project. Vite 6 will be the biggest release after Vite 2

In this video, Gina talks about 3D printing. 3D printing is a process of creating three-dimensional objects from a digital file. The most common way to 3D print is to use a hot glue gun to extrude melted plastic onto a build platform, layer by layer. This process can be done with a variety of materials, including PLA, ABS, and PETG. 3D printing is becoming increasingly popular due to its low cost and accessibility. There are a number of open-source software programs available that can be used to control 3D printers. One such program is OctoPrint, which was created by Gina . OctoPrint allows users to remotely monitor and control their 3D printers. It also includes a number of features that make it easy to use, such as a plugin system and safety checks. 3D printing is a complex process, but it is becoming increasingly accessible to people of all skill levels. With the right tools and resources, anyone can learn to 3D print.

his video is an interview with Filip, co-founder and CTO of Alokai, previously known as VueStorefront. The interviewee discusses modern enterprise e-commerce storefronts and how Alokai is used in enterprises. Here is a summary of the video in more detail: The video starts with an introduction to modern enterprise e-commerce storefronts. Filip then discusses his experience with Magento and other e-commerce platforms. Filip explains the concept of headless e-commerce and how it can be used to create more flexible and scalable e-commerce platforms. Filip discusses the importance of composability and how it can be used to create more modular and reusable e-commerce components. Filip provides some insights into the future of e-commerce and how AI will shape the industry. The video ends with a call to action for viewers to learn more about Alai and headless e-commerce.

GitHub Actions has become an integral part of any organization today, developers are using it for CI/CD every day at work and even in personal projects, thanks to generous free tier by GitHub.But with great power comes great responsibility, there are external entities waiting for you to make a mistake so that they can get access to your infrastructure. In this talk we will learn about: GitHub Actions Best Practices Securing your GitHub Actions This will be an interesting topic for everyone using GitHub Actions daily.

I spoke about how teams can use Nx to improve everyone's developer experience.