Error: No template for dependency: TemplateArgumentDependency

[codymikol]

Error: No template for dependency: TemplateArgumentDependency

[gajus]

Are you using webpack.optimize.DedupePlugin() plugin? Removing the latter plugin from my config solved the issue.

[nishp1]

Any thoughts?

Now getting following error with the upgrade of webpack to 1.7.0.

WARN [preprocess]: Can not load "webpack"!
  TypeError: Cannot read property 'filename' of null

[dennis-johnson-dev]

This seems to be our issue as well. @nishp1 Have you found a good workaround yet? cc @sokra

[nishp1]

I ended up upgrading webpack to latest version so that there is only version of webpack.

[idchlife]

Just now encountered error

/Users/myuser/www/react-test/scripts/node_modules/webpack/lib/Template.js:80
                            source.add(BalancePanel.render(module, dependencyTemplates, chunk));
                                       ^
ReferenceError: BalancePanel is not defined

When BalancePanel was my file and my class, not webpacks

I commented this

//var webpack = require('webpack');

and this

//new webpack.DefinePlugin({
//  'process.env': {
//    'NODE_ENV': JSON.stringify('production')
//  }
//})

in webpack.config.js file, also deleted webpack folder from node_modules, so exactly webpack from /usr/local/bin/webpack will be used.

Yep, I assume when using production plugin I will need to use it once and not in dev, otherwise I will end up with webpack trying to insert my classes in its source code (or I'm stupid)

[idchlife]

Addition. I also had to delete react and react-tools folders, after minification/stringification (or what it is), so they won't search for my class.

[eugene1g]

I had the same issue while using a global install of webpack and webpack-dev-server (current). With no other changes, it just started throwing that error one morning. I removed webpack and webpack-dev-server from global node_modules, installed both again and they worked fine again. Probably something going wrong with dependencies.

[gajus]

In addition, see webpack/webpack#1082.

[joshwiens]

Resolving as this is no longer valid in 2.2.0 and resolved for 1.x