[documentation] FLow about bundle-loader

[dignifiedquire]

Thanks, helped me!

[fabiomcosta]

Given you can also give a name to the bundle (ex: 'bundle-loader?lazy&name=bundle-name!./path), a more correct regexp would be:

module.name_mapper='^bundle-loader\?lazy[^!]*!\(.*\)$' -> '\1'

Thank you for the pointers!

[alexander-akait]

@sapottier why your need flow here? can your provide example use case?

[sapottier]

A small example who return 'Required module not fund' without the option.

// @flow
type routes = Array<{
  path: string,
  content: any, 
  header?: any,
  sidebar?: any,
  default?: boolean,
  restricted?: boolean | Array<string>,
  routes?: routes
}>;

import Example from 'bundle-loader?lazy!../views/Example/Example';
import Of from 'bundle-loader?lazy!../views/Of/Of';
import NestedRoute from 'bundle-loader?lazy!../views/NestedRoute/NestedRoute';

export const routerConfig: routes = [{
  path: '',
  content: Example,
  routes: [
    {
      path: 'example',
      content: Example,
      routes: [
        {
          path: 'of',
          content: Of,
          routes: [
            {
              path: 'nested-route',
              content: NestedRoute
            }
          ]
        }
      ]
    }
  ]
}];

[alexander-akait]

@sapottier What do you expect and what do you get (error, unexpected behavior)?

[sapottier]

Sorry, I have to be more precise. (sorry for my english)

Everything works well, except that when we use Flow, It does not understand 'bundle-loader?lazy!…' and return un error like 'Required module not fund'. To bypass this, a simple way is to configure Flow like previously explain. Also, maybe there is more to do by providing a flow-typed definition.

thank you,

Simon