Monorepos dont HAVE to be hard (...and why you should always use them) @JoshuaMorony
Monorepos dont HAVE to be hard (...and why you should always use them)  @JoshuaMorony
Uploaded April 2025 | Updated September 2026, 2 weeks ago
My Angular course: angularstart.com

Monorepos are often viewed as being complex and perhaps only suited to larger and more complex applications and organisations. This video shows how you can create a simple monorepo with pnpm workspaces that can be expanded with complexity as you need.

Get weekly content and tips exclusive to my newsletter: https://mobirony.ck.page/4a331b9076

My game dev channel: youtube.com/@joshmoronypixels

MY GEAR:
Keyboard: https://adm42.dev/?ref=3
Neovim setup: github.com/joshuamorony/lazyvim
Animations: motioncanvas.io

0:00 Introduction
1:10 Simple pnpm workspaces monorepo
3:17 Adding and configuring Nx
4:39 Build pipelines and deploys
6:20 Shared libraries and packages

#nx #pnpm #monorepo

- More tutorials: modernangular.com
Monorepos dont HAVE to be hard (...and why you should always use them)Angular THREE just released?!?The end of Angulars service with a subject approach?Why I use a view model stream for my Angular templatesRxJS made my code 5x shorter... but is it better?Should this be the future of Angular applications?Making route params easier with reactive codingngTemplateOutlet is WAY more useful than I realisedA workflow for complex open source contributionsRefactoring my ugliest code with signal view queriesThis new Angular primitive might actually be a viable alternative to RxJSA visual guide to switchMap and higher order observables
Joshua Morony |

Monorepos don't HAVE to be hard (...and why you should always use them)

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER