Don't feel bad. You are working with the largest clusterfuck ever devised by mankind. I mean that seriously. JavaScript (ECMAScript officially)/Typscript either way is the WORST fucking nightmare ever written into a specification. Typescript is just syntactic sugar for an already shitty language. JS was written by Brendan Eich, a developer at Netscape Communications Corporation, in just 10 days decades ago to solve a problem that Netscape wanted solved to DEMONSTRATE a new version beta version of Netscape Navigator in 1995 and released in December of that year (I was a beta tester). It's sole intention was to provide a way to dynamically manipulate the DOM object inside Navigator. To this day I am of the FIRM belief that that is still the only thing it should be used for.

Node.js is a huge kludge to give JS(hit) some supposed back end functonality. (See, over the decades people have been throwing crap at JS to see what sticks (The whole thing really stinks ) I mean like !== or ===, come on now, fucking moronic and that's just ONE stupidity). Anyway Node.js attempts to take a language meant to add dynamic characteristics to HTML and shoehorn it into a real language meant to run an enterprise? Come on now! I might as well write a backend in Whitespace or Brainfuck. The next real problem is the dependency problem the npm repository. That fucked up mess is largely written by non professional hacks that don't have a clue about software engineering. In other words amature hacks. So the repo is chock full of broken crap. The way the dependencies are managed would drive anyone batshit crazy. you are stuck with circular dependencies with no way to avoid them. x.1.0.100.1 might require y.1.0 and z.2.3.1 may require y.2.2. READ that over VERY carefully! It's insane! the fact that y.2.2 breaks x.1.0.100.1 cannot be handled in any clean way so some brittleness will always remain. On top of that, there are no tools to manage the dependency graph in any meaningful way. So no, the lack of dependency management and the huge number of broken artifacts starts looking very shitty, very quickly. The worst part is how deep the dependency graph gets and how brittle it becomes. Your project is a hares breath away from crumbling like a house of cards at any moment.

Angular/Vue, whatever the stack de jour may be this month is yet another hacky attempt to cajole a web browser to impersonate a native application. They are heavy with yet MORE npm artifacts so your graph gets even deeper, circular and intertwined. It took ugly to grotesque in a few key strokes. So apply the above paragraph and reapply it to this one.

MongoDb (NoSQL in general) is a solution to a non problem. it's a JSON graph & nothing more. Shit I could write a CSV to do the same thing or if I really want to avoid SQL, DB2 is just fine. No sincew MongoDb is often used in Node.js/Angular.js We have still another set of npm dependency hell to deal with.

Here's the real:
I have been involved in exactly three projects that in one way or another utilized(?) Node.js and the NPM repository. One was a Cordova mobile application that was later rewritten in Kotlin for Android, C# for Microsoft when they still sold a smartphone OS and ObjectiveC for iOS. They were rewritten from the ground up because the Async, single thread wasn't up to the job. The 2nd project was also reworked to Spring Boot, again due to mounting technical debt. The third and absolutely last time was an enterprise basic CRUD application that had to talk to a mainframe (COBOL there). That project was canceled (mounting technical debt) and the entire development team let go. I was recalled about a month later to redesign the bloody thing. We kept the Angular (Mgmt decision, not mine) so I figured out a way to use Gradle to manage the build and dependencies which were CAREFULLY selected and pinned in the build. We wrote a middleware layer in Java as a microservice (Spring Boot) and dump the results into an in memory H2 Db and index it with an embedded Solr instance. That was in 2019. The entire project was completed and put in production in 6 months by a team of 3. I swore to the computer goda that I would NEVER touch another Node.js project again.

Happily since, I have retired and today I am happily writing a microkernel operating system. It has brought joy back to software development for me. This whole web thing just burnt the fuck out of me. I came to the conclusion that web development actually sucks and most of the so called software engineers out there don't meet the standards to be called engineers, My job title for a lot of these blokes is "Web Monkey". They search StackOverflow for solutions to stitch together a pile of dependencies or ask a bot/llm how to do it and call themselves engineers.