nvr

nativescript-vue-router-extended

A simple Router for NativeScript-Vue, built on top of $navigateTo so to simplify routing between the pages

Showing:

Popularity

Downloads/wk

9

GitHub Stars

10

Maintenance

Last Commit

4d ago

Contributors

2

Package

Dependencies

2

License

Apache-2.0

Type Definitions

Built-In

Tree-Shakeable

No?

Categories

Readme

NativeScript Vue Router

NPM version Blazing Fast Code Coverage npm downloads install size

nativescript-vue-router-extended

NativeScript Vue Router brings easier routing handling to mobile apps, with an API compatibility with web version of Vue Router.

Please file an issue or make a PR if you spot any problems or you have any further requests regarding the functionality.

Table of Contents

Features

  • Same hooks and guards for mobile and web
  • Additional action dispatcher to dispatch actions to store automatically when changing routes
  • Vue-Router 4 API compatibility
  • NativeScript-Vue compatible
  • TypeScript Support out of the box

Prerequisites / Requirements

Nativescript 7.1+ is required for the plugin to run properly. It might be working on previous NS6 although the plugin is no longer officially supported for NativeScript 6.

Installation

ns plugin add nativescript-vue-router-extended

or

npm install nativescript-vue-router-extended

or

yarn add nativescript-vue-router-extended

NPM

Usage & Examples

To use this plugin you need to import it and initialize the router using createRouter() function. Global and per component Vue-Router hooks and guards are supported.

import Vue from "nativescript-vue";
import { createRouter } from "nativescript-vue-router-extended";

// Initialize Example Routes
import moviesPage from "./pages/movies.vue";

const routes = [
  {
    path: "/movies",
    component: moviesPage,
    meta: {
      isVertical: true,
      store: {
        showNavigationButtons: false,
      },
    },
  },
];

// Initialize Router
// Vue-Router settings are in 1st argument. 2nd one is used for extra NativeScript related settings
const router = createRouter(
  { routes },
  {
    // Optional settings below

    // Set first page to redirect to when there's no page to redirect back to
    routeBackFallbackPath: "/movies",

    // Do something straight before navigation or adjust NS routing settings
    routeToCallback: (to, options) => {
      // For example, change page navigation transition for the vertical on iOS
      if (to.meta.isVertical) {
        options.transition = {
          name: "fade",
        };
      }
    },

    // Do something straight before navigation or adjust NS routing settings
    routeBackCallback: (_to, options) => {
      //
    },

    // Set Vue Instance (Vue.prototype by default)
    vm: Vue.prototype,

    // Set a custom logger (console.log by default)
    logger: console.log,

    // Set custom frame, by default it's taken from @nativescript/core/ui/frame
    frame: Frame,
  }
);

// Register a global guard (optional)
// You can also use global router.beforeResolve guard and router.afterEach hook
router.beforeEach((to) => {
  // For example, verify per route access rules
  if (!canAccessRoute(to)) {
    return false;
  }

  return true;
});

// From now on you can access this.$router, this.$routeBack and special this.$routeTo inside of the components, example:
this.$routeTo("/movies", {
  // Clear History is a NativeScript setting
  clearHistory: true,
  props: {
    movieId: 12,
  },
});

New hooks for pages

You can use hooks directly on particular pages. It is discouraged to use them inside of mixins or components for the time being. Example below:

<template>
    <Page>
    </Page>
</template>

<script>

export default {
    name: 'movies',

    beforeRouteEnter(to, from, next) {
        // Do something before to enter to the route
        next((vm) => {
            // Do something once navigation is done
            // Instead of `this`, use `vm`
        });
    },

    beforeRouteLeave() {
        // Do something before to leave the route
        // You can use `this` inside of this hook
    },

    beforeRouteUpdate() {
        // Do something before to leave the route
        // before redirecting to another route with same path
        // You can use `this` inside of this hook
    },

    mounted() {
       // Output current route object with name, path etc.
       console.log(this.$route);
    },
};
</script>
NS EventMapped asDescription
navigatingFrombeforeRouteLeaveBefore user leaves the route
navigatingTobeforeRouteEnterBefore user enters a route
-beforeRouteUpdateBefore route is changed but view remains the same. This can happen when path is exactly the same but you change e.g. passed prop to the route. Please refer to Vue-Router docs for more details.
navigatedTobeforeRouteEnterTo trigger it properly you need to access component instance. You can use next(vm => ...) callback within beforeRouteEnter(). Please check Vue-Router docs for more details.
navigatedFrom-This event is tricky to control for developers. There is no exact mapping of it in the router. For store state cleanup use build-in meta dispatcher instead. For component state you could opt for using beforeRouteLeave().

TypeScript Support

If you need a TS support and it's not detected automatically in your project for some reason, you can use typings/shims.vue.d.ts to bring proper support in .vue files. You can specify it in your shims.vue.d.ts file (attention! Please ensure that path is relative to your node_modules directory):

/// <reference path="./node_modules/nativescript-vue-router-extended/typings/shims-vue.d.ts" />

API & Limitations

Vue Router compatibility

This plugin aims for compatibility with Vue Router 3+ and Vue Router 4+. Both should be easily supported. Please refer to Vue Router Docs for more information.

DOM & related hooks

There are some limitations like lack of DOM accessibility and related hooks and guards.

RouterLink Component

There's a lack of component due to performance reasons.

License

Apache License Version 2.0, January 2004

Troubleshooting

Please file an issue. You can use the template but it is not required. Just simply write what is your issue so we can try to reproduce and fix it.

Rate & Review

Great Documentation0
Easy to Use0
Performant0
Highly Customizable0
Bleeding Edge0
Responsive Maintainers0
Poor Documentation0
Hard to Use0
Slow0
Buggy0
Abandoned0
Unwelcoming Community0
100