CODEWITHSUNDEEP
javascriptwebpack
Adam Rackis
Adam Rackis

Reputation: 83356

Webpack - dynamic require and paths

My webpack.config file looks like this

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

module.exports = {
    entry: {
        app: './app'
    },
    output: {
        path: path.resolve(__dirname, 'build'),
        filename: '[name]-bundle.js'
    }
};

I have some dynamic requires that look like this

function loadModule(modName, cb, onErr){
    if (modName == 'contacts') require(['../modules/contacts/contacts', 'html!../modules/contacts/contacts.htm'], cb);
    else if (modName == 'tasks') require(['../modules/tasks/tasks', 'html!../modules/tasks/tasks.htm'], cb);
    else onErr();
}

Which work great. I'm seeing 1.1-bundle.js and 2.2-bundle.js getting added to my build folder.

The problem is, when these dynamic requires are triggered, I'm seeing 404s in my network tab, since webpack is trying to load 1-1.bundle.js from the root of my project, instead of the build folder where I told webpack to put it.

How do I correct this?

Upvotes: 2

Views: 4013

Answers (1)

KJ Tsanaktsidis
KJ Tsanaktsidis

Reputation: 1275

You probably need to set the public path- basically, you tell webpack where on your webserver it will find the built files, which for you seems to the the build folder.

{
    output: {
        path: path.resolve(__dirname, 'build'),
        filename: '[name]-bundle.js',
        publicPath: '/build/',
    },
}

Upvotes: 4

Related Questions