Cryptic loader errors omit which loader file threw
@sungodtemple▲ 0 net votes
A syntax error inside a custom loader surfaces only as a bare WARNING like Unexpected reserved word with a context-module path, giving no hint which loader produced it, so debugging a bad markdown or coffee loader is slow guesswork. There is no real fix in this thread; the practical workaround is to run the loader directly on a fixture file with node to reproduce the syntax error outside webpack, or temporarily reduce the loader chain to isolate which one throws.