I'd personally ignore Next.js and GraphQL, but would certainly (and personally have) invested in TypeScript. I am guessing that Next.js and GraphQL will be lon

I'd personally ignore Next.js and GraphQL, but would certainly (and personally have) invested in TypeScript. I am guessing that Next.js and GraphQL will be long-dead and obsolete "soon" (in the same way that e.g. jQuery & AngularJS were once also red-hot technologies but are now out of favor), but TypeScript really feels like it is here to stay with significant benefits. I guess this is a "learn technologies, not libraries" type thing? I was "forced" to learn TypeScript for Angular 2 (that was the library of choice at where I worked at the time) but now also use it for my personal stuff out of choice. Compared to pure JS it is a bit of a pain to get basic development up and running (since you need a TS -> JS compile step before you load it in the browser, unlike raw JS that you can just code and reload). For that I have created myself simple boiler-plate templates (1) that I use to bootstrap a new project so I can be up and running in a browser in 60 seconds etc (the template will do all the compilation and bundling for you using webpack) 1 - https://github.com/matt1/TsBoilerPlate https://github.com/matt1/TsBoilerPlate