Alternatives to Next.js logo

Alternatives to Next.js

Create React App, Gatsby, Hexo, LoopBack, and React are the most popular alternatives and competitors to Next.js.
2.1K
2.1K
+ 1
189

What is Next.js and what are its top alternatives?

Next.js is a minimalistic framework for server-rendered React applications.
Next.js is a tool in the Frameworks (Full Stack) category of a tech stack.
Next.js is an open source tool with 68.3K GitHub stars and 12.9K GitHub forks. Here鈥檚 a link to Next.js's open source repository on GitHub

Top Alternatives to Next.js

  • Create React App

    Create React App

    Create React apps with no build configuration.

  • Gatsby

    Gatsby

    Gatsby lets you build blazing fast sites with your data, whatever the source. Liberate your sites from legacy CMSs and fly into the future. ...

  • Hexo

    Hexo

    Hexo is a fast, simple and powerful blog framework. It parses your posts with Markdown or other render engine and generates static files with the beautiful theme. All of these just take seconds. ...

  • LoopBack

    LoopBack

    A highly-extensible, open-source Node.js framework that enables you to create dynamic end-to-end REST APIs with little or no coding. Connect to multiple data sources, write business logic in Node.js, glue on top of your existing services and data, connect using JS, iOS & Android SDKs. ...

  • React

    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • Angular Universal

    Angular Universal

    It executes on the server, generating static application pages that later get bootstrapped on the client. This means that the application generally renders more quickly, giving users a chance to view the application layout before it becomes fully interactive. ...

  • React Router

    React Router

    React Router is a complete routing solution designed specifically for React.js. It painlessly synchronizes the components of your application with the URL, with first-class support for nesting, transitions, and server side rendering. ...

  • Hugo

    Hugo

    Hugo is a static site generator written in Go. It is optimized for speed, easy use and configurability. Hugo takes a directory with content and templates and renders them into a full html website. Hugo makes use of markdown files with front matter for meta data. ...

Next.js alternatives & related posts

Create React App logo

Create React App

849
802
4
Create React apps with no build configuration
849
802
+ 1
4
PROS OF CREATE REACT APP
  • 2
    No config, easy to use
  • 2
    Maintained by React core team
CONS OF CREATE REACT APP
  • 1
    No SSR

related Create React App posts

Adebayo Akinlaja
Engineering Manager at Andela | 22 upvotes 路 627.1K views

I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen鈥攕ince I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

See more

I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis 聽for cache and other time sensitive operations.

We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

See more
Gatsby logo

Gatsby

2.3K
1.9K
93
Free, open source framework for building blazing fast websites and apps with React
2.3K
1.9K
+ 1
93
PROS OF GATSBY
  • 20
    Generated websites are super fast
  • 14
    Fast
  • 11
    GraphQL
  • 8
    Progressive Web Apps generation
  • 7
    Reusable components (React)
  • 7
    Easy to connect with lots of CMS via official plugins
  • 6
    Allows to use markdown files as articles
  • 4
    Images
  • 4
    Static-sites
  • 3
    List of starters as base for new project
  • 3
    All the benefits of a static website + React+GraphQL
  • 3
    Easy to connect with Drupal via official plugin
  • 2
    Open source
  • 1
    Gitlab pages integration
CONS OF GATSBY
  • 5
    No ssr
  • 3
    Documentation isn't complete.
  • 2
    Flash of unstyled content issues
  • 1
    Too many dependencies
  • 1
    Slow builds
  • 1
    Very slow builds
  • 1
    For-profit

related Gatsby posts

Johnny Bell
Software Engineer at Weedmaps | 77 upvotes 路 1.1M views

I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

See more
Ronan Levesque
Software engineer at Algolia | 18 upvotes 路 223.5K views

A few months ago we decided to move our whole static website (www.algolia.com) to a new stack. At the time we were using a website generator called Middleman, written in Ruby. As a team of only front-end developers we didn't feel very comfortable with the language itself, and the time it took to build was not satisfying. We decided to move to Gatsby to take advantage of its use of React , as well as its incredibly high performances in terms of build and page rendering.

See more
Hexo logo

Hexo

273
316
68
A fast, simple & powerful blog framework, powered by Node.js
273
316
+ 1
68
PROS OF HEXO
  • 17
    Ease of deployment
  • 13
    Uses NodeJS and npm
  • 12
    Easy GitHub Pages publishing
  • 10
    Powerful templating
  • 7
    Useful tools and plugins
  • 4
    Easy intergrating with js
  • 3
    Open source
  • 2
    Blazing Fast
CONS OF HEXO
    Be the first to leave a con

    related Hexo posts

    LoopBack logo

    LoopBack

    240
    431
    21
    Build modern API applications that require complex integrations
    240
    431
    + 1
    21
    PROS OF LOOPBACK
    • 7
      Easy Database Migration
    • 7
      Need a nodejs ReST-API, DB, AAA, Swagger? Then loopback
    • 4
      Code generator
    • 2
      The future of API's
    • 1
      GraphQL
    CONS OF LOOPBACK
    • 6
      Community is slow
    • 1
      Backward compatibility

    related LoopBack posts

    Samuel Olugbemi
    Software Engineer at Payzone UK | 6 upvotes 路 100K views
    Shared insights
    on
    LoopBack
    ExpressJS
    at

    I use LoopBack because it is: * It is truly and Unbelievably Extensible * it is default integrated with OpenAPI (Swagger) Spec Driven REST API * I write lesser codes, because most of the user stories have been covered using the code generation * It's documentation is more compact and well detailed than ExpressJS * It is very easy to learn, hence you can build a basic Rest API App in minutes * It has built in NPM packages required to build my Rest API which saves me time on installation and configuration * The Datasource/Service/Controller concept is just Brilliant (that's mostly all you need to get your app speaking with an External API services) * The support for SOAP and Rest API services is amazing!

    See more
    Shared insights
    on
    NestJS
    Jest
    LoopBack

    We inherited this project and the backend is using LoopBack v3. I haven't taken a look at Loopback.io v4, but I'm planning to replace it. The reason being is that Loopback v3 documentation is a bit confusing and we are having trouble packaging the build using Webpack. Not to mention, integrating unit tests (latest Jest).

    I still think Loopback is a great tool, but their documentation is really "messy" and hard to navigate through. There's also a constraint of time from our side. So what's the best option out there?

    Should I try upgrading to Loopback v4, or trying other stuff? (i.e. NestJS)

    Thanks!

    See more
    React logo

    React

    98.2K
    77.3K
    3.8K
    A JavaScript library for building user interfaces
    98.2K
    77.3K
    + 1
    3.8K
    PROS OF REACT
    • 751
      Components
    • 651
      Virtual dom
    • 558
      Performance
    • 484
      Simplicity
    • 436
      Composable
    • 174
      Data flow
    • 159
      Declarative
    • 123
      Isn't an mvc framework
    • 113
      Reactive updates
    • 110
      Explicit app state
    • 31
      JSX
    • 23
      Learn once, write everywhere
    • 18
      Uni-directional data flow
    • 16
      Easy to Use
    • 14
      Works great with Flux Architecture
    • 10
      Great perfomance
    • 8
      Built by Facebook
    • 6
      Javascript
    • 5
      TypeScript support
    • 5
      Speed
    • 4
      Awesome
    • 4
      Easy to start
    • 4
      Feels like the 90s
    • 4
      Scalable
    • 3
      Functional
    • 3
      Server side views
    • 3
      Hooks
    • 3
      Fancy third party tools
    • 2
      Props
    • 2
      Simple
    • 2
      Has functional components
    • 2
      Great migration pathway for older systems
    • 2
      SSR
    • 2
      Fast evolving
    • 2
      Simple, easy to reason about and makes you productive
    • 2
      Very gentle learning curve
    • 2
      Excellent Documentation
    • 2
      Rich ecosystem
    • 2
      Super easy
    • 2
      Has arrow functions
    • 2
      Strong Community
    • 2
      Closer to standard JavaScript and HTML than others
    • 2
      Scales super well
    • 2
      Just the View of MVC
    • 2
      Server Side Rendering
    • 2
      Cross-platform
    • 1
      Sharable
    • 1
      Start simple
    • 1
      Obama
    • 1
      Every decision architecture wise makes sense
    • 1
      Permissively-licensed
    • 1
      Beautiful and Neat Component Management
    • 1
      Fragments
    • 1
      Sdfsdfsdf
    • 1
      Allows creating single page applications
    • 1
      Split your UI into components with one true state
    CONS OF REACT
    • 32
      Requires discipline to keep architecture organized
    • 20
      No predefined way to structure your app
    • 19
      Need to be familiar with lots of third party packages
    • 6
      JSX
    • 6
      Not enterprise friendly
    • 1
      One-way binding only
    • 1
      State consistency with backend neglected

    related React posts

    Vaibhav Taunk
    Team Lead at Technovert | 31 upvotes 路 1.5M views

    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

    See more
    Johnny Bell
    Software Engineer at Weedmaps | 26 upvotes 路 377.2K views
    Shared insights
    on
    Vue.js
    React

    I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

    It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

    See more
    Angular Universal logo

    Angular Universal

    284
    291
    12
    A technology that renders Angular applications on the server
    284
    291
    + 1
    12
    PROS OF ANGULAR UNIVERSAL
    • 2
      Complete Framework
    • 2
      Typescript
    • 2
      Same existing code base for both SPA and SSR
    • 1
      Easy setup
    • 1
      Static site generator
    • 1
      Dynamic rendering
    • 1
      Is not React
    • 1
      Server rendering and code splitting
    • 1
      SEO
    CONS OF ANGULAR UNIVERSAL
    • 1
      Not React

    related Angular Universal posts

    React Router logo

    React Router

    1.4K
    940
    12
    A complete routing solution for React.js
    1.4K
    940
    + 1
    12
    PROS OF REACT ROUTER
    • 12
      Because there's not alternative
    CONS OF REACT ROUTER
      Be the first to leave a con

      related React Router posts

      ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

      ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

      React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

      styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

      React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

      Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

      See more

      I'm creating a website with React in my free time, and this is my first time doing this. So far, I've worked with React and React Router, but migrating to Next.js or Gatsby would cover Routing and SEO, which I currently cannot work with. Most things I read say that Next.js is the best solution, but I am trying to decide whether it is worth the time and effort to recreate the site for SEO and speed purposes. Does anyone have suggestions?

      See more
      Hugo logo

      Hugo

      987
      877
      171
      A Fast and Flexible Static Site Generator written in Go
      987
      877
      + 1
      171
      PROS OF HUGO
      • 43
        Lightning fast
      • 26
        Single Executable
      • 22
        Great development community
      • 22
        Easy setup
      • 19
        Open source
      • 12
        Write in golang
      • 6
        LiveReload built in
      • 6
        Not HTML only - JSON, RSS
      • 5
        Hacker mindset
      • 3
        Easy to customize themes
      • 3
        Gitlab pages integration
      • 1
        Very fast builds
      • 1
        Easy to learn
      • 1
        Well documented
      • 1
        Fast builds
      CONS OF HUGO
      • 4
        No Plugins/Extensions
      • 2
        Template syntax not friendly
      • 1
        Quick builds

      related Hugo posts

      John-Daniel Trask
      Co-founder & CEO at Raygun | 19 upvotes 路 158.2K views
      Shared insights
      on
      .NET
      WordPress
      Hugo
      at

      There鈥檚 no doubt WordPress is a great CMS, which is very user friendly. When we started the company, our blog wasn鈥檛 really our top priority, and it ended up being hosted on a fairly obscure server within our setup, which didn鈥檛 really change much until recently when things become harder to manage and make significant updates.

      As our marketing team increased, the amount of traffic that found us through our content marketing increased. We found ourselves struggling to maintain our Wordpress install given the amount of theme updates, plugins and security patches needing to be applied. Our biggest driver to find an alternative solution however was just how slow Wordpress is at serving content to the end user. I know there will be die hard fans out there with ways to set things up that mean WordPress sites can load quickly, but we needed something a lot more streamlined.

      We could see in our own Real User Monitoring tool that many users were experiencing page load speeds of over five seconds, even longer in worst case scenarios. Hugo is an open source static site generator that has enabled us to reduce load times by over 500% and make our blog far more maintainable across the whole team.

      The Raygun marketing site runs on a .NET CMS called N2 but we plan to swap that out with Hugo as well in future.

      #StaticSiteGenerators #SelfHostedBloggingCms #SupportSalesAndMarketing

      See more
      Josh Dzielak
      Co-Founder & CTO at Orbit | 5 upvotes 路 208.6K views
      Shared insights
      on
      Jekyll
      Hugo

      Earlier this year, I migrated my personal website (dzello.com) from Jekyll to Hugo. My goal with the migration was to make the development environment as pleasant as possible and to make it really easy to add new types of content. For example, I knew I wanted to add a consulting page and some portfolio-style pages to show off talks I had given and projects I had worked on.

      I had heard about how fast Hugo was, so I tried it out with my content after using a simple migration tool. The results were impressive - the startup and rebuild times were in milliseconds, making the process of iterating on content or design less cumbersome. Then I started to see how I could use Hugo to create new page types and was very impressed by the flexibility of the content model. It took me a few days to really understand where content should go with Hugo, but then I felt very confident that I could create many different types of pages - even multiple blogs if I wanted - using a consistent syntax and with full control of the layouts and the URLs.

      After about 6 months, I've been very happy with the results of the migration. The dev environment is light and fast and I feel at ease adding new pages and sections to the site.

      See more