Disable Vue Router warnings

[CernyMatej]

Is it possible to disable these Vue Router warnings?

I am dynamically adding the routes in a middleware in Nuxt (based on a db request) and these warnings are very annoying.
They disappear when I use a regular <a> tag, but then the page will do a full reload on every navigation.

I searched online a lot but sadly didn't find any reasonable solution.

Edit:
Looks like it's not possible... 😕
https://github.com/vuejs/router/blob/f776cbe1098596f53b5c2f696d29e1c02afd1fc1/packages/router/src/router.ts#L543

[Yordan-Ramchev]

It's not a good solution, but you could suppress/hide this exact warning using https://vuejs.org/api/application.html#app-config-warnhandler The bad thing is that you won't get a warning when there is a Vue Router location missmatch

[CernyMatej]

Hi, thank you but this config option is sadly ignored in production. I would like to disable them in production as well as I'm getting about 30-40 warnings printed to the console with every request.

[L0st1]

If your routes doesnt have a route before you insert it, you might need route-matching-syntax
Just like this. Of course, this is for an application that is not Nuxt.js

const routes: Array<RouteRecordRaw> = [
  {
    path: "/",
    name: "base-empty",
    component: EmptyView,
  },
  {
    path: "/about",
    name: "base-about",
    component: () => import("../views/AboutView.vue"),
  },
  // eliminating warnings  [Vue Router warn]: No match found for location with path
  // if i have some routes(they all startsWith "app-") will be inserted after initialization 
  {
    path: "/app-:appName(.*)",
    name: 'MicroApp',
    component: MicroAppRoute, 
  },
  {
    path: '/:pathMatch(.*)*', 
    name: 'NotFound',
    redirect: "/NotFound"
  }
];

[CernyMatej]

Hi, thank you for your suggestion, but this, sadly, isn't a very good solution for my use case. I have the slugs saved in a database along with the page type they correspond to, so there could be a route /foo which should resolve to a blog page and a route /bar that should resolve to a product page. There can be thousands of products, so it isn't possible to include all of them in the router routes definition, nor do they have a prefix that I could use to differentiate them.