npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

spa-auto-route

v1.1.1

Published

Provide automated route solution for SPAs based on vuejs.

Downloads

19

Readme

spa-auto-route

Usage

  1. import spa-auto-route;
    import autoRoute from 'spa-auto-route';
  2. generate routes;
    const routes = autoRoute(require.context('@/view', true, /index\.vue$/), /\/component\//);
  3. put the routes into vue-router.
    new Router({
      mode: 'history',
      base: ROUTER_PREFIX,
      routes: [
        ...routes,
      ],
    });

API

autoRoute(requiredFiles, excludeRegExp)

  1. requiredFiles: must be generated by require.context
  2. excludeRegExp: files path RegExp which you don't want to put into router
  3. if a route has nested routes(multi-level nesting is supported), you should demostrate them in vue instance:
    export default {
      nestedRoutes: [
        // the string is child route folder name(case sensitive).
        'childRoute1',
        'childRoute2',
      ],
      name: 'AFatherRoute',
      data() {
        return {
          ...
        };
      },
    }
  4. when use nestedRoutes, you can alse write a 'redirect' property
    export default {
      nestedRoutes: [
        // the string is child route folder name(case sensitive).
        'childRoute1',
        'childRoute2',
      ],
      // you'd better use a component's name rather than a path, because path may be modified occasionally. And name is shorter than path!
      redirect: {
        name: 'AllotBillHome',
      },
      // or
      // redirect: 'path/to/fatherroute/childroute2',
      name: 'AFatherRoute',
      data() {
        return {
          ...
        };
      },
    }
  5. You can add a 'alias' property in component
    export default {
      name: 'ARoute',
      alias: 'a/route/anthor/name',
      // multiple aliases
      alias: ['/xxx', 'yyy'],
      data() {
        return {
          ...
        };
      },
    }
  6. You can add a 'routeMeta' in component, it's meta property in vue-router
    export default {
      name: 'ARoute',
      alias: 'a/route/anthor/name',
      // multiple aliases
      routeMeta: {
        requiresAuth: true,
      },
      data() {
        return {
          ...
        };
      },
    }

Tips

  1. in spa-auto-route file path is router path accurately, so organize your folders reasonably;
  2. route'name is token from vue instance's name, please make sure that every vue component has a unique name;
  3. routes which nest other child routes should be flat with child routes, like this:
    ├── config.js
    ├── fatherRoute.vue
    ├── childRoute1
    │   └── index.vue
    │   └── config.js
    ├── childRoute2
    │   └── index.vue
    │   └── config.js