Add support for exportPathMap in development

[timneutkens]

Paths defined in exportPathMap now work in development.
Makes https://github.com/zeit/next.js/wiki/Centralizing-Routing obsolete.

[arunoda]

I'm not sure about the functionality of this. Is this a core alternative to next-routes?

Functionality wise I like this. The problem is the name of the routeMap exportPathMap. Since it's something we defined for next-export.

It might be also great, if we can do this via a plugin.

[timneutkens]

I'm not sure about the functionality of this. Is this a core alternative to next-routes?

It's not.

Functionality wise I like this. The problem is the name of the routeMap exportPathMap. Since it's something we defined for next-export.

This change is specifically to make development of static sites better, since previously users would run into the issue that they'd have to add a custom server to develop a static site, which doesn't make sense.

[arunoda]

This change is specifically to make development of static sites better, since previously users would run into the issue that they'd have to add a custom server to develop a static site, which doesn't make sense.

Ah cool. Then this will be great.

[arunoda]

This looks great.
Try to add comment in the place I shown below.

[arunoda]

Shall we add a comment on why we are doing this?

[arunoda]

@timneutkens awesome.
Let's take this.