
The reason I like PERN with TS is that it's performant and type-safe, specifically TS and PG are a good match. That will be the real challenge/test of my knowledge. My next step is to follow the PERN (Postgres, Express, react, Node) stack course by FCC and add in TS myself. I'll need the time to digest what I did and take some notes, but I feel a lot more comfortable building with TypeScript than I did on Friday night (it's Sunday night) The only thing I haven't done is put it all together. I'll be interested to know how things develop with the new JS types that was announce recently - though that might take a while (years) to reach production JS. There's just a bit more to know and write. TS, apart from the learning curve, isn't bad.

It was not easy to find a good resource online about how to set up a TS / PG project which also had raw SQL (no ORM - Object-Relational Mapper) so that I could understand how the queries are used in the API.Express/Node + Postgres API with CRUD operations.Brad at Traversy Media showing me the path forward for setting up TS with Express/Node.Simple instantiation of an Express/Node app with types.It makes more sense now and I'll be leveraging the React-TypeScript Cheat-Sheet more going forwards.React-TypeScript is what I knew less and was a bit trickier to conceptualise before doing the FCC tutorial.

This weekend I created 3 repos to get to grips with TS at all levels of the stack:
