A developer updates code dependencies and integrates pnpm workspaces into a monorepo application. The walkthrough covers modifying the abstract repository, configuring the pnpm-workspace.yaml file for efficient dependency management, and updating Docker files to optimize production image builds across multiple services.
Length 6:03
Captions English (Generated), Spanish (Auto-translated), French (Auto-translated), Korean (Auto-translated), Portuguese (Auto-translated), Vietnamese (Auto-translated) #coding #monorepo #pnpm #docker #typescript #dependencies #software architecture #vscode #web development #tutorial
0:00 All right, so in this lecture, I wanna walk you through some course 0:03 updates that we 0:03 have now that we're on the latest versions of all of our dependencies 0:08 at the time of this recording. Of course, I'm gonna keep this course up to date 0:12 and publish more updates in the future. 0:14 So let's go over the latest breaking changes we have to our application 0:18 with the latest dependencies. So our first step is going to be to head 0:22 back into our abstract repository. 0:26 So if we head into our libs common database abstract 0:30 repository. So here on the latest versions of 0:33 Mongoose, we can 0:34 see that our types have actually changed for filter 0:38 query. So if you're coming from the previous 0:40 lecture, our project used to use the 0:42 filter query type for all of these filter queries that we 0:46 passed in to find one and more. But now this is 0:49 simply changed to be query filter instead. 0:52 So everywhere that you're passing filter query, this should simply 0:56 just be query filter. They just swapped the order of this type. 1:01 So this one is very simple to update. 1:04 So this is really the only code changes we need to support the latest dependencies. 1:08 However, on the latest package versions 1:10 and infrastructure, I 1:11 wanna introduce a new concept to our 1:15 project, which is a pnpm workspace. 1:18 So 1:19 recall, in our application, we have our separate apps that 1:23 have their own individual package JSON files. 1:26 Now, the advantage of this or the advantage we're supposed to be 1:30 getting is 1:30 that each app here can define dependencies that are 1:34 specific just for this particular application, right? 1:37 We don't need passport and bcrypt, these auth related 1:41 dependencies inside of the other applications inside of th- 1:45 their final production build that we create with a Docker file.
The rest of the transcript is for members.
Sign in 