[next] context-loader bugs

[thangngoc89]

There is 2 bugs with latest content-loader:

• Default loader should not be required at the top of the file. This would require user install remark-* while they don't need them.
• webpack's loader parser remove all function from query ==> no custom engine

I suggest we ditch webpack loader's query completely and use a custom field in webpack config

[MoOx]

• we will use require() for this
• Loader query function, regex, and object, support webpack/core#13

[thangngoc89]

Ok. But not a good solution imho. This requires an extra file just for rendering markdown (or whatever).

[MoOx]

import === require, we should just call the require if no custom rendered passed.

[thangngoc89]

I mean an extra file in user's project.

[MoOx]

No need for an extra file. We can just remove import defaultRenderer from "./default-renderer"import defaultRenderer from "./default-renderer" and use const renderer = query.renderer || require("./default-renderer").

[thangngoc89]

And what about custom renderer ? user puts result of require.resolve to it ? Or we move the loader config to webpack config ? (like postcss-loader)