refactor: add webpack-defaults

[michael-ciniawsky]

Fix

• Error Message

Test

• Add Tests

Docs

• Add LOADER.md (JSDoc)
• Update README.md

Refactor

• Add webpack-defaults
• Support CoffeeScript v2
• Load Sourcemaps only if setup (options.sourceMap)

TODO

• add schema-utils (added but disabled atm)

Fixes #14, #21, #31, #32, #33

[michael-ciniawsky]

schema-utils could be patched later any time, the schema and logic is implemented, just need to shape schema-utils itself a bit, otherwise good to go for @beta meanwhile

[michael-ciniawsky]

Ready to

[joshwiens]

Let's hold off until a decision on the Jest topic has been made before we land any conversions that negate all the Jest goodness.

[michael-ciniawsky]

Yep agreed, the loader works that was the baseline for the moment I will try to out a different approach later (it's 'planned' since a few days now:)) to start webpack in the test instead of making a 'test bundle'. Is there anything shipped already somewhere ?

[joshwiens]

If you want a good example of where I want to go in the short term with testing, check the testing setup in the css-loader new-loader branch. Snapshot testing is much like scoping commit messages, valuable where applicable.

[michael-ciniawsky]

But in the new loader branch, it doesn't 'run' through webpack atm and just loader.call({}, fixture) etc. For coverage and 'basic' Input => Output testing this is totally fine, but when a loader relies on the Loader API at least one 'real world' scenario must be tested somehow :)

[joshwiens]

Hence the long term goal which will require a Jest preprocessor to handle the webpack magic portion while not compromising the Jest sugarness.