Frontend

The senior frontend map is the baseline. You still need that list. This post is the rest of the slice: the names you will meet on the other side of the contract, and what changes when you own both sides of a bug at 2 a.m. I am a frontend-shaped senior who has crossed that line more than once. Years ago that looked like leaving a Laravel API and an AngularJS client for Spring Boot and Angular. The useful lesson was not “learn Java.” It was how much of the job lives in the seam. ...

If you are early in the job, you need names. You cannot aim at a skill you have never heard of. Roadmap.sh is still the best public map of those names. Use it. What it cannot tell you is the altitude. A mid who can list Vite, Playwright, TypeScript generics, and a state library is still a mid if the work they own is a ticket. Senior is the size of the thing you can be handed, and what happens to it. ...

As an Angular developer, staying updated with the latest trends in frontend development is crucial for keeping your skills relevant and your projects modern. The frontend landscape is constantly evolving, and embracing these trends can help you create better-performing, more maintainable, and more engaging applications. Here are some of the latest trends you should be aware of: 1. Micro Frontends Micro Frontends are gaining significant traction as they allow large applications to be divided into smaller, manageable pieces, each developed and deployed independently. This approach enhances scalability and team productivity, especially in large organizations. Micro Frontends. ...

Managing multiple Angular projects can be a daunting task, especially as teams grow and codebases become more complex. In this article, we’ll explore three common approaches for managing multiple Angular projects: Micro Frontends, Monorepo, and Reusable Shared Module. We’ll compare their advantages, disadvantages, and suitability for different scenarios to help you make an informed decision for your Angular projects. Micro Frontends Consider a large e-commerce platform comprising several distinct sections, including product catalog, shopping cart, checkout, and user profile. With micro frontends, each section can be developed and deployed independently as a separate micro frontend. This enables different teams to work autonomously on their respective sections, improving development speed, scalability, and flexibility. ...

In Angular development, creating reusable shared modules is a powerful way to encapsulate common functionality, UI components, services, and styles that can be used across different projects or repositories. In this guide, we’ll walk through the process of creating a reusable shared module from scratch, covering directory structures, component/service/directive creation, shared styles, and both development (npm link) and production (npm publish) use cases. Companion resource Companion Project Try the working example in your browser or inspect the full source code behind this article. github.com/omidfarhang/example-projects/examples/angular-shared-library-workspace Open live demo View on GitHub Step 1: Generate a Library The first step is to generate an Angular library project within your workspace using the Angular CLI: ...

This is the companion for Why and How. It proves one thing: a host page can load separately built Angular and React bundles as custom elements, pass a message attribute down, and take a microfrontend:message event back. It does not prove Module Federation, independent production deploys, or a shared design system. npm run dev builds the remotes, then starts one Qwik server that serves them from public/mfes/. Rust WebAssembly is a shell helper for CPU work, not a fourth micro frontend. ...

Once you have a reason to split the UI, the next decision is how the pieces become one page. That assembly step is composition: the host application — the shell — decides where each slice renders and what it is allowed to see. There are a few honest ways to do it. I picked one for the companion: the browser loads separately built bundles and mounts them as custom elements — HTML tags the host did not compile. That is client-side composition. It is not the only option, and it is not a production platform by itself. ...

A micro frontend is a slice of a web UI that one team can build, test, and ship without waiting on the rest of the page. Picture two teams and two pipelines on one checkout: catalog can go out on Tuesday while payments is still in review. That independence is the whole reason to do this. It is also the cost. Someone still has to own the page those slices land on, and someone has to keep the agreement between them from rotting. ...

Angular 2.0 shipped in September. We are on 2.4 now, and the release train is already moving — Angular 4 is being talked about openly. I have been building with it since October, migrating a medium-sized internal dashboard that lived in AngularJS for three years. This is not a tutorial and not a verdict. It is a field report from someone who still dreams in $scope sometimes. The context nobody warns you about If you spent years on AngularJS, you did not “upgrade.” You rewrote. Google offers ngUpgrade to run both frameworks side by side, and we tried it for two weeks before giving up. Our app had too many directives, too much implicit magic, and too many $watches buried in places nobody remembered. We picked a greenfield module, scaffolded it with the CLI, and started porting feature by feature. ...