Alternatives to Vue Router logo

Alternatives to Vue Router

vuex, React Router, axios, Nuxt.js, and styled-components are the most popular alternatives and competitors to Vue Router.
293
213
+ 1
0

What is Vue Router and what are its top alternatives?

It is the official router for Vue.js. It deeply integrates with Vue.js core to make building Single Page Applications with Vue.js a breeze.
Vue Router is a tool in the JavaScript Framework Components category of a tech stack.
Vue Router is an open source tool with 18.8K GitHub stars and 5.2K GitHub forks. Here鈥檚 a link to Vue Router's open source repository on GitHub

Top Alternatives to Vue Router

  • vuex
    vuex

    Vuex is a state management pattern + library for Vue.js applications. It serves as a centralized store for all the components in an application, with rules ensuring that the state can only be mutated in a predictable fashion. It also integrates with Vue's official devtools extension to provide advanced features such as zero-config time-travel debugging and state snapshot export / import. ...

  • 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. ...

  • axios
    axios

    It is a Javascript library used to make http requests from node.js or XMLHttpRequests from the browser and it supports the Promise API that is native to JS ES6. ...

  • Nuxt.js
    Nuxt.js

    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. ...

  • styled-components
    styled-components

    Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 馃拝 ...

  • Storybook
    Storybook

    It is an open source tool for developing UI components in isolation for React, Vue, and Angular. It makes building stunning UIs organized and efficient. ...

  • Ant Design
    Ant Design

    An enterprise-class UI design language and React-based implementation. Graceful UI components out of the box, base on React Component. A npm + webpack + babel + dora + dva development framework. ...

  • Angular CLI
    Angular CLI

    A command-line interface tool that you use to initialize, develop, scaffold, and maintain Angular applications. You can use the tool directly in a command shell, or indirectly through an interactive UI such as Angular Console. ...

Vue Router alternatives & related posts

vuex logo

vuex

1.2K
854
7
Centralized State Management for Vue.js.
1.2K
854
+ 1
7
PROS OF VUEX
  • 2
    Debugging
  • 2
    Zero-config time-travel
  • 2
    Centralized State Management
  • 1
    Easy to setup
CONS OF VUEX
    Be the first to leave a con

    related vuex posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH | 22 upvotes 路 1.2M views

    Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

    • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
    • Vue Styleguidist as our style guide and pool of developed Vue.js components
    • Vuetify as Material Component Framework (for fast app development)
    • TypeScript as programming language
    • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
    • ESLint, TSLint and Prettier for coding style and code analyzes
    • Jest as testing framework
    • Google Fonts and Font Awesome for typography and icon toolkit
    • NativeScript-Vue for mobile development

    The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

    • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
    • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
    • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
    • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
    • Large scaling. Vue.js can help to develop pretty large reusable templates.
    • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
    See more

    Vue.js vuex Vue Router Quasar Framework Electron Node.js npm Yarn Git GitHub Netlify My tech stack that helps me develop quickly and efficiently. Wouldn't want it any other way.

    See more
    React Router logo

    React Router

    2.2K
    1K
    12
    A complete routing solution for React.js
    2.2K
    1K
    + 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
      axios logo

      axios

      1.9K
      336
      0
      Promise based HTTP client for the browser and node.js
      1.9K
      336
      + 1
      0
      PROS OF AXIOS
        Be the first to leave a pro
        CONS OF AXIOS
          Be the first to leave a con

          related axios posts

          Nuxt.js logo

          Nuxt.js

          1.5K
          1.3K
          293
          The Vue.js Framework
          1.5K
          1.3K
          + 1
          293
          PROS OF NUXT.JS
          • 46
            SSR
          • 41
            Automatic routes
          • 27
            Middleware
          • 22
            Hot code reloading
          • 19
            Easy setup, easy to use, great community, FRENCH TOUCH
          • 17
            Static Websites
          • 17
            SPA
          • 16
            Plugins
          • 14
            Code splitting for every page
          • 14
            Custom layouts
          • 11
            Automatic transpilation and bundling (with webpack and
          • 10
            Modules ecosystem
          • 9
            Easy setup
          • 8
            Amazing Developer Experience
          • 7
            Vibrant and helpful community
          • 7
            Pages directory
          • 6
            Not React
          • 2
            Its Great for Team Development
          CONS OF NUXT.JS
          • 4
            Still vue 2
          • 2
            Not React
          • 1
            Not Next

          related Nuxt.js posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH | 22 upvotes 路 1.2M views

          Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

          • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
          • Vue Styleguidist as our style guide and pool of developed Vue.js components
          • Vuetify as Material Component Framework (for fast app development)
          • TypeScript as programming language
          • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
          • ESLint, TSLint and Prettier for coding style and code analyzes
          • Jest as testing framework
          • Google Fonts and Font Awesome for typography and icon toolkit
          • NativeScript-Vue for mobile development

          The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

          • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
          • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
          • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
          • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
          • Large scaling. Vue.js can help to develop pretty large reusable templates.
          • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
          See more
          Giordanna De Gregoriis
          Jr Fullstack Developer at Stefanini Inspiring | 8 upvotes 路 162.2K views

          TL;DR: Shall I keep developing with Nuxt.js 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

          Long version: We have an old web application running on AngularJS and Bootstrap for frontend. It is mostly a user interface to easily read and post data to our engine.

          We want to redo this web application. Started from scratch using the newest version of Angular 2+ and Material Design for frontend. We haven't even finished rewriting half of the application and it is becoming dreadful to work on.

          • The cold start takes too much time
          • Every little change reload the whole page. Seconds to minutes of development lost looking at a loading blank page just changing css
          • Code maintainability is getting worse... again... as the application grows, since we must create everytime 5 files for a new page (html, component.ts, module.ts, scss, routing.ts)

          I'm currently trying to code a Proof of Concept using Nuxt.js and Tailwind CSS. But the thing is, Vue.js 3 is out and has interesting features such as the composition API, teleport and fragments. Also we wish to use the Vite frontend tooling, to improve our time developing regardless of our application size. It feels like a better alternative to Webpack, which is what Nuxt 2 uses.

          I'm already trying Nuxt.js with the nuxt-vite experimental module, but many nuxt modules are still incompatible from the time I'm posting this. It is also becoming cumbersome not being able to use teleport or fragments, but that can be circumvented with good components.

          What I'm asking is, what should be the wisest decision: keep developing with Nuxt 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

          See more
          styled-components logo

          styled-components

          1.3K
          521
          11
          Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps...
          1.3K
          521
          + 1
          11
          PROS OF STYLED-COMPONENTS
          • 11
            Very easy to use and integrate
          CONS OF STYLED-COMPONENTS
            Be the first to leave a con

            related styled-components posts

            Johnny Bell

            For Stack Decisions I needed to add Markdown in the decision composer to give our users access to some general styling when writing their decisions. We used React & GraphQL on the #Frontend and Ruby & GraphQL on the backend.

            Instead of using Showdown or another tool, We decided to parse the Markdown on the backend so we had more control over what we wanted to render in Markdown because we didn't want to enable all Markdown options, we also wanted to limit any malicious code or images to be embedded into the decisions and Markdown was a fairly large to import into our component so it was going to add a lot of kilobytes that we didn't need.

            We also needed to style how the markdown looked, we are currently using Glamorous so I used that but we are planning to update this to Emotion at some stage as it has a fairly easy upgrade path rather than switching over to styled-components or one of the other cssInJs alternatives.

            Also we used React-Mentions for tagging tools and topics in the decisions. Typing @ will let you tag a tool, and typing # will allow you to tag a topic.

            The Markdown options that we chose to support are tags: a, code, u, b, em, pre, ul, ol, li.

            If there are anymore tags you'd love to see added in the composer leave me a comment below and we will look into adding them.

            #StackDecisionsLaunch

            See more

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

            Storybook

            946
            463
            0
            Build bulletproof UI components faster
            946
            463
            + 1
            0
            PROS OF STORYBOOK
              Be the first to leave a pro
              CONS OF STORYBOOK
                Be the first to leave a con

                related Storybook posts

                Robert Zuber

                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
                Ant Design logo

                Ant Design

                862
                1.4K
                225
                A set of high-quality React components
                862
                1.4K
                + 1
                225
                PROS OF ANT DESIGN
                • 43
                  Lots of components
                • 34
                  Polished and enterprisey look and feel
                • 22
                  TypeScript
                • 20
                  Easy to integrate
                • 18
                  Es6 support
                • 17
                  Beautiful and solid
                • 16
                  Beautifully Animated Components
                • 15
                  Quick Release rhythm
                • 14
                  Great documentation
                • 14
                  Typescript support
                • 11
                  Short Code
                • 1
                  Easy to customize Forms
                CONS OF ANT DESIGN
                • 18
                  Less
                • 8
                  Large File Size
                • 7
                  Close
                • 4
                  Poor accessibility support
                • 1
                  Sdf
                • 1
                  Dangerous to use as a base in component libraries
                • 1
                  Gago
                • 0
                  D

                related Ant Design posts

                Sarmad Chaudhary
                Founder & CEO at Ebiz Ltd. | 9 upvotes 路 528K views

                Hi there!

                I just want to have a simple poll/vote...

                If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:

                1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.

                2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.

                Your advice would help a lot! Thanks in advance :)

                See more
                Shared insights
                on
                Material-UIMaterial-UIAnt DesignAnt Design

                Hi, I start building an admin dashboard with next.js and looking for a frontend framework ( components ready ). So I end up with Ant Design and Material-UI, but I never built a project with these two.

                Here is a list of my requirements.

                1. Good documentation.
                2. easy CRUD ( date picker and date range picker bundled )
                3. built-in multi-lang feature or Great 3rd library support
                4. Admin dashboard template
                5. well code maintenance

                Which is better for the long run?

                See more
                Angular CLI logo

                Angular CLI

                845
                689
                0
                A command line interface for Angular
                845
                689
                + 1
                0
                PROS OF ANGULAR CLI
                  Be the first to leave a pro
                  CONS OF ANGULAR CLI
                    Be the first to leave a con

                    related Angular CLI posts

                    Vaibhav Taunk
                    Team Lead at Technovert | 31 upvotes 路 1.9M 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

                    Picked Angular 2 as framework since Angular CLI made it easy to get started on a self-contained frontend web project with TypeScript for easier development -- thanks to intellisense extensions for Visual Studio Code, hassle-free browser compatibility with the built-in Babel transpiler and packaging with the built-in Webpack configuration.

                    See more