vue-router-next | The official router for Vue.js | Router library

 by   vuejs TypeScript Version: v4.0.12 License: MIT

kandi X-RAY | vue-router-next Summary

kandi X-RAY | vue-router-next Summary

vue-router-next is a TypeScript library typically used in Networking, Router, Vue applications. vue-router-next has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

The official router for Vue.js

            kandi-support Support

              vue-router-next has a medium active ecosystem.
              It has 1657 star(s) with 389 fork(s). There are 33 watchers for this library.
              It had no major release in the last 12 months.
              There are 21 open issues and 393 have been closed. On average issues are closed in 0 days. There are 16 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of vue-router-next is v4.0.12

            kandi-Quality Quality

              vue-router-next has no bugs reported.

            kandi-Security Security

              vue-router-next has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

            kandi-License License

              vue-router-next is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              vue-router-next releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vue-router-next
            Get all kandi verified functions for this library.

            vue-router-next Key Features

            No Key Features are available at this moment for vue-router-next.

            vue-router-next Examples and Code Snippets

            No Code Snippets are available at this moment for vue-router-next.

            Community Discussions


            Vue-router4 - Passing object with won't pass dynamic data
            Asked 2021-Apr-20 at 15:23

            I went through this vue-router@4.05 object params which is somewhat related. There is a mention of this in that thread, but I am still confused.

            I am also trying to pass some data using the :to attribute of the router link component. I have made two pens to showcase the issue:

            Pen 1 passes an object that is defined within the routes definition - successfully.

            Pen 2 is trying to pass a dynamic object and instead of the actual object it gets a string with [Object object] as described in the github issue.

            console output:

            [Vue warn]: Invalid prop: type check failed for prop "repository". Expected Object, got String with >value "[object Object]". at at at at

            So, if I get this straight, ultimately you cant pass a dynamic object cos it's parsed, but you can pass a static object?

            I have tried with props: true and everything, I am trying the function mode solution as a more complex example




            Answered 2021-Apr-20 at 15:23

            Passing arbitrary data (not defined in route definition as params) was never supported in Vue-router and never worked as expected. Check my answer on the question you linked

            Your example v1 works only because the value of repository defined in props function of the route overwrites the repository value passed from router-link through params (which is repository: "[object Object]" as you can see in the console)

            So, if I get this straight, ultimately you cant pass a dynamic object cos it's parsed, but you can pass a static object?


            1. You can't pass any object using $router.push or router-link (even it "sort of worked" in Vue-router 3 - again, see my linked answer)

            2. You can define props on the route definition as an object or as a function returning object and it's properties will by passed to your component's props without any encoding or anything. But this is very different from using $router.push or router-link as the data does not come from source route but from router itself...



            useRoute is undefined
            Asked 2021-Mar-26 at 07:28

            I'm trying to use useRoute in a vue 2.6 application but it's undefined:



            Answered 2021-Mar-26 at 07:28

            There is no useRouter in vue router only in vue router next I know both pages look like they are for vue-router and none of the next content would suggest it's not for vue-router but the url indicates it's for vue router next.

            It's nice to be prepared for the future but currently vue 2 is still installed when doing a yarn add vue so it would be nice if the documentation had a header indicating this is about a completely different project that just happens to have the same name and logos.

            I suspect looking at this question I'm sht out of luck trying to get vue-route parameters in the composition-api setup function.


            With provide/inject I can get route props from every component:



            How to declare TypeScript type interface for custom meta fields in Vue Router v4?
            Asked 2020-Sep-22 at 00:48

            With Vue Router version 4, which is currently in beta.11 in vue-router-next repo, there is a documentation page about how to define meta fields custom type interface with TypeScript.



            Answered 2020-Sep-22 at 00:48

            Their documentation is wrong or at best incomplete.

            A Module Augmentation uses the same syntax as an Ambient Module declaration and is only considered an augmentation when it is within a module file itself. A module is defined, as per the ECMAScript specification, as a file containing one or more top level import or export statements.

            The snippet in a file that is not a module does exactly what you've noticed. It supplants any other types for the 'vue-router' package instead of augmenting them. But we want to augment that package's types, not replace them.

            However, a declare module statement that is intended as a declaration, not an augmentation, must be in a file that is, conversely, not a module. That is, in a file not containing any top level import or export statements.

            To resolve this, move the declare module 'vue-router' {...} to a separate file (say, augmentations.d.ts), and make that file a module by beginning it with export {}.



            How to use vue-router-next without bundler?
            Asked 2020-Sep-12 at 12:19

            The previous version of vue-router uses the global application instance and mounts the plugin automatically:



            Answered 2020-Sep-12 at 12:19
            • Home
            • Foo
            • Bar


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install vue-router-next

            Via CDN: <script src=""></script>
            In-browser playground on CodeSandbox
            Add it to an existing Vue Project: npm install vue-router@4


            Vue Router is part of the Vue Ecosystem and is an MIT-licensed open source project with its ongoing development made possible entirely by the support of Sponsors. If you would like to become a sponsor, please consider:. Get started with the documentation.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone vuejs/vue-router-next

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Reuse Pre-built Kits with vue-router-next

            Consider Popular Router Libraries


            by remix-run


            by ReactTraining


            by vuejs


            by gorilla


            by angular-ui

            Try Top Libraries by vuejs


            by vuejsTypeScript


            by vuejsTypeScript


            by vuejsJavaScript


            by vuejsJavaScript


            by vuejsTypeScript