→ Home ←

Nextjs, TypeScript, Vercel, GraphQL, and Apollo - Nextgen Static Site Generation

Cover Image for Nextjs, TypeScript, Vercel, GraphQL, and Apollo - Nextgen Static Site Generation
Andrew Ross
Andrew Ross


First and foremost, TypeScript puts the super in superset, especially in a team environment. State management in React can be cumbersome, which is why I consider GraphQL and Apollo to be the dynamic duo. That said, Redux and Recoil each have their use-cases as well. As far as primary prebuilts are concerened, the "Next.js" framework is top-notch. It removes the otherwise tedious process of manually configuring Webpack to support a server-side rendering app from the equation. It saves time, streamlines optimization, and is blazing fast to enhane UX.


TypeScript is a JavaScript superset, it supports additional properties such as annotations, decorators, generics, interfaces, enums, modules, tuples, and more. It offers a uniqe advantage of having preconfigured polyfill support. How? There is a primary tsconfig.json file in the root of every TypeScript project. Within this file, the "target" key has a corresponding value that specifies the ECMAScript target version (JavaScript's actual name) which the TypeScript will be compiled into on build. So, while we are enjoying the benefits of coding with modern syntax (ESNext), this code compiles down to ES5 (2009) JavaScript upon generating a production build. Why does this matter? This greatly bolsters the accessibility of the platform for users still running legacy operating systems or using legacy browsers. For example, Microsoft just terminated support for Windows 7 users and Internet Explorer 11 which means that they will no longer receive updates. By compiling down to ES5, this content is just accessible to legacy users as it is to users running more current software. The other plus? No longer having to rely on often bulky polyfill libraries.