What is Next.js?
Who uses Next.js?
Why developers like Next.js?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Next.js in their tech stack.
I just finished a web app meant for a business that offers training programs for certain professional courses. I chose this stack to test out my skills in graphql and react. I used Node.js , GraphQL , MySQL for the #Backend utilizing Prisma as a database interface for MySQL to provide CRUD APIs and graphql-yoga as a server. For the #frontend I chose React, styled-components for styling, Next.js for routing and SSR and Apollo for data management. I really liked the outcome and I will definitely use this stack in future projects.
When we started thinking about technology options for our own Design System, we wanted to focus on two primary goals
- Build a design system site using design system components - a living prototype
- Explore new ways of working to position our technical capabilities for the future
We have a small team of developers responsible for the initial build so we knew that we couldn’t spend too much time maintaining infrastructure on the Backend. We also wanted freedom to make decisions on the Frontend with the ability to adapt over time.
For this first iteration we decided to use Node.js, React, and Next.js. Content will be managed via headless CMS in prismic.io.
- Next.js so that we can run React serverside without worrying about server code.
- prismic.io so that our content is accessible via API and our frontend is fully independent.
Webpack and Babel are configured out of the box for #ServerSideRendering, #TreeShaking, and other nice #JS features.
We use Next.js because it's the best framework for server side rendering on react right now. Our platform handle websites for clients, which means on all of those websites we need to worry about the SEO, and that google can find them on the search results. Next made it extremely easy in combination with express to be able to render dynamic routes based on the user configuration for their website. We were able to build a small "Wix" in our own platform. 😊
Having a single Next.js that handles several websites at the same time, with a lot of custom-unique components can be a pain in the a**, with TypeScript our team can see what props are needed and what kind of data needs to be passed to it in order to work correctly.
- Zero setup. Use the filesystem as an API
- Automatic server rendering and code splitting
- Data fetching is up to the developer
- Anticipation is the key to performance
- Simple deployment