108 exclude list

[samanpwbb]

This is a more abstracted fix for #108, an alternative to #109. Here, user may provide an excludeCompileNodeModules option as an alternative to compileNodeModules, in order to exclude specific modules. By default, GL JS 2+ gets placed in the excludeList. Needs tests and docs.

[samanpwbb]

Could use a couple more tests:

• Error case if user provides both include and exclude lists
• Case where use provides their own set of exclude modules

[samanpwbb]

Okay, this is now working. @kepta could you give this a look and lmk if the concept seems okay? If so I'll wrap up tests and docs.

[jingsam]

It would be better to update readme to tell users that compileNodeModules and excludeCompileNodeModules are mutually exclusive， we can not set both。

[davidtheclark]

One idea that could prevent the need for mutually exclusive configuration properties: make a breaking change to the compileNodeModules API to make its value an object that allows for more complex choices. I'd say this situation shows that the current interface is probably too limited; an object is nicely extensible.

For example, with an object you could do something like this:

compileNodeModules: { include: ['*'], exclude: ['mapbox-gl'] }

compileNodeModules: { exclude: ['mapbox-gl'] } // many * is the default include: value

One other opinion if you're still brainstorming: I'm wondering if the complexity of trying to distinguish the GL JS version is more trouble than it's worth, since the underreact user should be aware of their GL JS version and can decide to compile or not compile based on that.

[dereklieu]

I agree with the feedback here to either consolidate or document the include/exclude interface.

I also agree with removing special consideration for gl-js v2 in the configuration generator. This could be something to call out in the read me though, since it's true that many consumers of this project may also use gl-js.

[kepta]

One option is to directly export the include webpack property and let folks deal with it directly. We can add an example in the README on the best way to handle with gl-js versions.
That said, I am okay with any of the above approaches but would prefer whichever adds the least complexity to this aging codebase.

[jingsam]

I suggest just mapping includeCompileNodeModules and excludeCompileNodeModules options to webpack rule.include and rule.exclude. No more hack. Less code, less bug, and less burden.