> - it can be the same language as the backend, that's a huge advantage (no need to change context, you can more easily have the team for backend and frontend)

> - it can be the same language as the backend, that's a huge advantage (no need to change context, you can more easily have the team for backend and frontend) Having used TypeScript for both frontend and backend for several projects, I say this isn't as necessary as you might imagine. The real context is whether you're coding for your frontend or your backend and that context will happen even if the languages are the same. You can use same set of libraries but usually they don't really overlap either.