sourceMap not always available in `SourceMapDevToolPlugin` #955

sairion opened this Issue Apr 8, 2015 · 1 comment


None yet
2 participants

sairion commented Apr 8, 2015

I'm not still sure why this is happening (investigating, not reproducible in local env), but reporting:

TypeError: Cannot read property 'sources' of null
    at Tapable.<anonymous> (/some/path/node_modules/webpack/lib/SourceMapDevToolPlugin.js:63:19)
    at (native)
    at Tapable.<anonymous> (/some/path/node_modules/webpack/lib/SourceMapDevToolPlugin.js:44:84)
    at Array.forEach (native)
    at Tapable.<anonymous> (/some/path/node_modules/webpack/lib/SourceMapDevToolPlugin.js:43:11)
    at Tapable.applyPlugins (/some/path/node_modules/webpack/node_modules/tapable/lib/Tapable.js:26:37)
    at Tapable.<anonymous> (/some/path/node_modules/webpack/lib/Compilation.js:543:10)
    at (/some/path/node_modules/webpack/node_modules/tapable/lib/Tapable.js:69:11)
    at Tapable.<anonymous> (/some/path/node_modules/webpack/lib/optimize/UglifyJsPlugin.js:136:4)
    at Tapable.applyPluginsAsync (/some/path/node_modules/webpack/node_modules/tapable/lib/Tapable.js:73:13)


Not completely sure yet, but it seems this commit break my company's CI ;) sourceMap isn't always avaiable, maybe. I will try to fix to earlier version (@1.7.3) to dodge the problem and see what's happening in @1.8.0.


This comment has been minimized.

Show comment
Hide comment

sokra commented Apr 8, 2015

@sokra sokra closed this Apr 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment