Alternatives to Nuxt.js logo

Alternatives to Nuxt.js

Meteor, Next.js, Gridsome, Bootstrap, and Animate.css are the most popular alternatives and competitors to Nuxt.js.
348
212
+ 1
100

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

Nuxt.js presets all the configuration needed to make your development of a Vue.js application enjoyable. You can use Nuxt.js for SSR, SPA, Static Generated, PWA and more.
Nuxt.js is a tool in the Front-End Frameworks category of a tech stack.

Nuxt.js alternatives & related posts

related Meteor posts

Trey Tacon
Trey Tacon
Node.js
Node.js
Meteor
Meteor

Mixmax was originally built using Meteor as a single monolithic app. As more users began to onboard, we started noticing scaling issues, and so we broke out our first microservice: our Compose service, for writing emails and Sequences, was born as a Node.js service. Soon after that, we broke out all recipient searching and storage functionality to another Node.js microservice, our Contacts service. This practice of breaking out microservices in order to help our system more appropriately scale, by being more explicit about each microservice鈥檚 responsibilities, continued as we broke out numerous more microservices.

See more
Trey Tacon
Trey Tacon
AWS Elastic Beanstalk
AWS Elastic Beanstalk
AWS Elastic Load Balancing (ELB)
AWS Elastic Load Balancing (ELB)
nginx
nginx
Go
Go
Amazon EC2
Amazon EC2
Node.js
Node.js
Meteor
Meteor
Mixmax
Mixmax

As Mixmax began to scale super quickly, with more and more customers joining the platform, we started to see that the Meteor app was still having a lot of trouble scaling due to how it tried to provide its reactivity layer. To be honest, this led to a brutal summer of playing Galaxy container whack-a-mole as containers would saturate their CPU and become unresponsive. I鈥檒l never forget hacking away at building a new microservice to relieve the load on the system so that we鈥檇 stop getting paged every 30-40 minutes. Luckily, we鈥檝e never had to do that again! After stabilizing the system, we had to build out two more microservices to provide the necessary reactivity and authentication layers as we rebuilt our Meteor app from the ground up in Node.js. This also had the added benefit of being able to deploy the entire application in the same AWS VPCs. Thankfully, AWS had also released their ALB product so that we didn鈥檛 have to build and maintain our own websocket layer in Amazon EC2. All of our microservices, except for one special Go one, are now in Node with an nginx frontend on each instance, all behind AWS Elastic Load Balancing (ELB) or ALBs running in AWS Elastic Beanstalk.

See more

related Next.js posts

Robert Zuber
Robert Zuber
CTO at CircleCI | 15 upvotes 270K views
atCircleCICircleCI
Cypress
Cypress
Percy
Percy
Jest
Jest
Apollo
Apollo
GraphQL
GraphQL
Emotion
Emotion
TypeScript
TypeScript
Storybook
Storybook
React
React
Next.js
Next.js

We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

See more
Divine Bawa
Divine Bawa
at PayHub Ghana Limited | 13 upvotes 101K views
Apollo
Apollo
Next.js
Next.js
styled-components
styled-components
React
React
graphql-yoga
graphql-yoga
Prisma
Prisma
MySQL
MySQL
GraphQL
GraphQL
Node.js
Node.js

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.

See more
Gridsome logo

Gridsome

28
52
6
28
52
+ 1
6
Build blazing fast websites for any CMS or data with Vue.js & GraphQL 鈿★笍馃挌
Gridsome logo
Gridsome
VS
Nuxt.js logo
Nuxt.js
Bootstrap logo

Bootstrap

49.9K
7K
7.5K
49.9K
7K
+ 1
7.5K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
Bootstrap logo
Bootstrap
VS
Nuxt.js logo
Nuxt.js

related Bootstrap posts

Ganesa Vijayakumar
Ganesa Vijayakumar
Full Stack Coder | Module Lead | 15 upvotes 397.1K views
SonarQube
SonarQube
Codacy
Codacy
Docker
Docker
Git
Git
Apache Maven
Apache Maven
Amazon EC2 Container Service
Amazon EC2 Container Service
Microsoft Azure
Microsoft Azure
Amazon Route 53
Amazon Route 53
Elasticsearch
Elasticsearch
Solr
Solr
Amazon RDS
Amazon RDS
Amazon S3
Amazon S3
Heroku
Heroku
Hibernate
Hibernate
MySQL
MySQL
Node.js
Node.js
Java
Java
Bootstrap
Bootstrap
jQuery Mobile
jQuery Mobile
jQuery UI
jQuery UI
jQuery
jQuery
JavaScript
JavaScript
React Native
React Native
React Router
React Router
React
React

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Francisco Quintero
Francisco Quintero
Tech Lead at Dev As Pros | 13 upvotes 145.4K views
atDev As ProsDev As Pros
Trello
Trello
Slack
Slack
Keen
Keen
Bootstrap
Bootstrap
Create React App
Create React App
React
React
Google Maps
Google Maps

For Etom, a side project. We wanted to test an idea for a future and bigger project.

What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

You kind of need a map to work as a proxy between the software and Google Maps API.

We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

Thanks to all the people behind Create React App it's easier to start any React application.

We also chose a module called Reactstrap which is Bootstrap UI in React components.

An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

See more
Animate.css  logo

Animate.css

7.4K
39
0
7.4K
39
+ 1
0
A library of CSS animations
    Be the first to leave a pro
    Animate.css  logo
    Animate.css
    VS
    Nuxt.js logo
    Nuxt.js

    related Foundation posts

    Lee Benson
    Lee Benson
    Koa
    Koa
    React Router
    React Router
    Foundation
    Foundation
    Semantic UI
    Semantic UI
    Bootstrap
    Bootstrap
    PostCSS
    PostCSS
    Less
    Less
    Sass
    Sass
    styled-components
    styled-components
    React Helmet
    React Helmet
    Webpack
    Webpack
    TypeScript
    TypeScript
    JavaScript
    JavaScript
    Apollo
    Apollo
    GraphQL
    GraphQL
    React
    React
    #JSX
    #React.
    #Css
    #StyledComponents.
    #Async
    #HTML
    #GraphQL
    #Apollo

    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
    UIkIt logo

    UIkIt

    635
    125
    199
    635
    125
    + 1
    199
    A lightweight and modular front-end framework for developing fast and powerful web interfaces
    UIkIt logo
    UIkIt
    VS
    Nuxt.js logo
    Nuxt.js

    related Semantic UI posts

    Lee Benson
    Lee Benson
    Koa
    Koa
    React Router
    React Router
    Foundation
    Foundation
    Semantic UI
    Semantic UI
    Bootstrap
    Bootstrap
    PostCSS
    PostCSS
    Less
    Less
    Sass
    Sass
    styled-components
    styled-components
    React Helmet
    React Helmet
    Webpack
    Webpack
    TypeScript
    TypeScript
    JavaScript
    JavaScript
    Apollo
    Apollo
    GraphQL
    GraphQL
    React
    React
    #JSX
    #React.
    #Css
    #StyledComponents.
    #Async
    #HTML
    #GraphQL
    #Apollo

    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
    Material-UI logo

    Material-UI

    559
    511
    156
    559
    511
    + 1
    156
    React components for faster and easier web development
    Material-UI logo
    Material-UI
    VS
    Nuxt.js logo
    Nuxt.js

    related Material-UI posts

    GraphQL
    GraphQL
    Apollo
    Apollo
    Material-UI
    Material-UI
    React Router
    React Router
    React
    React
    #MovieGeeks

    I just finished tweaking styles details of my hobby project MovieGeeks (https://moviegeeks.co/): The minimalist Online Movie Catalog

    This time I want to share my thoughts on the Tech-Stack I decided to use on the Frontend: React, React Router, Material-UI and React-Apollo:

    1. React is by far the Front-End "framework" with the biggest community. Some of the newest features like Suspense and Hooks makes it even more awesome and gives you even more power to write clean UI's

    2. Material UI is a very solid and stable set of react components that not only look good, but also are easy to use and customize. This was my first time using this library and I am very happy with the result

    3. React-Apollo in my opinion is the best GraphQL client for a React application. Easy to use and understand and it gives you awesome features out of the box like cache. With libraries like react-apollo-hooks you can even use it with the hooks api which makes the code cleaner and easier to follow.

    Any feedback is much appreciated :)

    See more
    Adebayo Akinlaja
    Adebayo Akinlaja
    Engineering Manager at Andela | 13 upvotes 20.9K views
    Bit
    Bit
    Create React App
    Create React App
    Material Kit
    Material Kit
    TypeScript
    TypeScript
    Evergreen
    Evergreen
    Material-UI
    Material-UI
    React
    React

    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
    Dojo logo

    Dojo

    477
    11
    0
    477
    11
    + 1
    0
    A Progressive TypeScript Framework for Modern Web Apps
      Be the first to leave a pro
      Dojo logo
      Dojo
      VS
      Nuxt.js logo
      Nuxt.js
      Polymer logo

      Polymer

      320
      305
      152
      320
      305
      + 1
      152
      A new library built on top of Web Components, designed to leverage the evolving web platform on modern...
      Polymer logo
      Polymer
      VS
      Nuxt.js logo
      Nuxt.js

      related Polymer posts

      Ido Shamun
      Ido Shamun
      at The Elegant Monkeys | 5 upvotes 15.6K views
      atDailyDaily
      Polymer
      Polymer
      React
      React
      Vue.js
      Vue.js
      #Frontend

      For developing our #frontend applications, we decided to use Vue.js . Being such an easy to learn library, compared to React for example, it made everything so easy. At first we started with Polymer but the existing tooling and small community at the time made us look for alternatives.

      See more
      Adam Rabinovitch
      Adam Rabinovitch
      Global Technical Recruiting Lead & Engineering Evangelist at Beamery | 3 upvotes 29.2K views
      atBeameryBeamery
      Polymer
      Polymer
      Aurelia
      Aurelia
      Vue.js
      Vue.js
      Angular 2
      Angular 2
      React
      React
      AngularJS
      AngularJS
      #Hiring

      At Beamery we had a large, AngularJS app, built over several years. Our clients were happy, but we were not. We had several problems: Building new features was slow. AngularJS doesn鈥檛 scale nicely. Features clash with each other. Isolation doesn鈥檛 come as standard, you have to work hard to keep features separate. It takes time to get it right. #Hiring was hard, for all the reasons listed above. The app was slower than it needed to be because AngularJS was never built for speed. We wanted to render half a million contacts, and Angular was fighting us all the way.

      As time went by it become harder to find developers who would willingly choose AngularJS over React Angular 2 , Vue.js , Aurelia or Polymer .

      So we faced a choice. We could throw it all away and start again, we could upgrade to Angular 5, or the awesome option - we could use micro frontends. We chose the awesome option.

      See more

      related Vuetify posts

      Paul Whittemore
      Paul Whittemore
      Developer and Owner at Appurist Software | 15 upvotes 84.3K views
      Fastly
      Fastly
      Electron
      Electron
      vuex
      vuex
      Vue.js
      Vue.js
      Quasar Framework
      Quasar Framework
      Vuetify
      Vuetify
      Node.js
      Node.js
      ExpressJS
      ExpressJS
      Fastify
      Fastify

      I'm building most projects using: Server: either Fastify (all projects going forward) or ExpressJS on Node.js (existing, previously) on the server side, and Client app: either Vuetify (currently) or Quasar Framework (going forward) on Vue.js with vuex on Electron for the UI to deliver both web-based and desktop applications for multiple platforms.

      The direct support for Android and iOS in Quasar Framework will make it my go-to client UI platform for any new client-side or web work. On the server, I'll probably use Fastly for all my server work, unless I get into Go more in the future.

      Update: The mobile support in Quasar is not a sufficiently compelling reason to move me from Vuetify. I have decided to stick with Vuetify for a UI for Vue, as it is richer in components and enables a really great-looking professional result. For mobile platforms, I will just use Cordova to wrap the Vue+Vuetify app for mobile, and Electron to wrap it for desktop platforms.

      See more
      Bulma logo

      Bulma

      238
      119
      6
      238
      119
      + 1
      6
      Free, open source, & modern CSS framework based on Flexbox
      Bulma logo
      Bulma
      VS
      Nuxt.js logo
      Nuxt.js
      Flat UI logo

      Flat UI

      88
      82
      0
      88
      82
      + 1
      0
      Free Bootstrap Framework and Theme
      Flat UI logo
      Flat UI
      VS
      Nuxt.js logo
      Nuxt.js
      Vue CLI logo

      Vue CLI

      82
      67
      0
      82
      67
      + 1
      0
      Standard Tooling for Vue.js Development
        Be the first to leave a pro
        Vue CLI logo
        Vue CLI
        VS
        Nuxt.js logo
        Nuxt.js