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

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

[michael-ciniawsky]

The ESLint Config is interpreted a bit tbh 😛 , but I would like to open discussion about a few of these rules anyways import/order, import/no-dynamic-require, global-require, no-param-reassign

[joshwiens]

Personally, I'd just disable eslint for any test utility files, they have little to no bearing on code quality where it really matters.

[joshwiens]

To the point, the rules you mentioned in the comment above have an effect on code readability / quality for source files and are there for a reason imo.

For something like webpack.build.js where it has no effect on the above, I would sooner disable the linting outright in the file than disable rules across the organization that have a positive effect on overall quality.

[joshwiens]

global-require should not be disabled by default as it's frowned upon in general.

In the certain cases where it's necessary, it should be disabled inline or in the .eslintrc on a case by case basis and set to warn from error so they can be addressed at a later date where applicable.

[michael-ciniawsky]

Still import/order no-param-reassign are 'conflicting' with the loader logic, the first for style/readability the latter for sourcemaps

import fs from 'fs'
import path from 'path'

import { getOptions } from 'loader-utils'
import { validateOptions } from 'schema-utils'

import helper from './helper'

if (options.sourceMap) {
  map = updateMap(map)
}

[joshwiens]

import/order - webpack-contrib/eslint-config-webpack#7

[michael-ciniawsky]

"repository": {
    "type": "git",
    "url": "git+https://github.com/webpack-contrib/coffee-loader.git"
  },
  "bugs": {
    "url": "https://github.com/webpack-contrib/coffee-loader/issues"
  },
  "homepage": "https://webpack.js.org",

[joshwiens]

@michael-ciniawsky - As we work through these, just create a named branch in the origin repo, makes it easier to test out for the group. You have org wide write access, far simpler than maintaining a fork :)