Throw exception or provide info message when route's component is null

[mortyccp]

What problem does this feature solve?

Currently, route's component can be null and it give no information and error. Provide information or raising error can help users to catch they have some import issues when they use

import * as components from './components'

export default [
  {
    path: '/accounts',
    component: components.AccountsListView,
    name: 'accountsListView'
  },
  {
    path: '/accounts/create',
    component: components.CreateEditAccounts,
    name: 'createAccounts'
  }
]

So if components.CreateEditAccounts is null, they will know what went wrong easier.

What does the proposed API look like?

Raise error when component is null or log info message.

[posva]

for anybody picking this up: make sure to check it only in dev mode

[serge1peshcoff]

I will try to implement this the next week if nobody would be faster than me

[posva]

There's already a pr 😉

[posva]

Note to myself, this could be solved through typings

[deckar01]

This issue also produces unexpected behavior when routes without components have child routes. See #2908.

@posva The MR for this is 18 months old. Can we close that and remove the has PR label?

[amitkeinan9]

I see that no one had touched this issue since March. May I try?

[Robert-Kovalcuk]

is it still possible to solve the issue?