prabh-62

Managing dependecies in a monorepo 📦

It's a good practice to keep dependencies and frameworks up to date and align with the rest of the ecosystem. In a monorepo, maintenance becomes a burden if there isn't regular housekeeping.

Backend - .NET

Setting up Central Package Management is a must in a .NET solution. All it takes is a single XML file.

• dotnet new packagesprops

prabh-62

.NET architecture: class libraries, entry points, and thin controllers

Put most code in class libraries so new hosts (API, worker, AI, mobile) plug in without duplicating rules. Controllers should stay thin; fat controllers make reuse and testing expensive.

---

1. Core idea

Business rules and workflows live in class libraries. Entry points are thin shells that connect those libraries to HTTP, queues, schedules, chat, etc.

prabh-62

[user]
email = abc@gmail.com
name = ABC
[merge]
tool = vscode
[mergetool "vscode"]
cmd = code --wait $MERGED
[init]
defaultBranch = main
[fetch]

prabh-62

Uninstall globally installed Angular CLI. Use npx

When we install @angular/cli globally, we pin the version of ng binary to a specific version which results in us using out-of-date ng binary most of the times(Angular CLI team publishes new version on a weekly basis). And if we are working in a team, we could be out of sync with the rest of developers since each dev might have different version of @angular/cli installed.

Check if you have @angular/cli installed globally

• NPM npm list --global --depth 0
• Yarn yarn global list

prabh-62

How monorepo eventually save $$?

What is monorepo?

When we store all(or most) of our source code in a single git repository, we term the git repository as mono-repository. Mono-repository usually contains multiple applications, and several reusable libraries.

Updating/Debugging library

Typically, when a developer needs to debug a library source code, they have to first clone the library source code and then somehow link the library and application source code together.

Also, if a developer has to update a library, they have to again clone the library source code, make updates and then verify the resulting package. Upon verification, dev publishes newer version of the library.

prabh-62

#!/bin/bash

rootCheck="sudo"

# Format SYstemInfo Output
printToFile(){
	printf "\n\n" >> $FILE
	printf '%*s\n' "${COLUMNS:-$(tput cols)}" '' | tr ' ' - >> $FILE
	echo -e "$(tput setaf 1) ${1} $(tput setaf 7) " >> $FILE
	printf '%*s\n' "${COLUMNS:-$(tput cols)}" '' | tr ' ' -  >> $FILE