module.exports = {
    entry: {
        "demo-perseus": "./src/demo-perseus.js",
        "frame-perseus": "./src/perseus-frame.js",
    },
    output: {
        path: "./build",
        publicPath: "/build/",
        filename: "[name].js",
    },
    devServer: {
        historyApiFallback: "/build/",
    },
    plugins: require('./webpack.config.js').plugins,
    module: require('./webpack.config.js').module,
};

module.exports = {
    entry: {
        "demo-perseus": "./src/demo-perseus.js",
        "frame-perseus": "./src/perseus-frame.js",
    },
    output: {
        path: "./build",
        publicPath: "build/",
        filename: "[name].js",
    },
    devServer: {
        historyApiFallback: "/build/",
    },
    plugins: require('./webpack.config.js').plugins,
    module: require('./webpack.config.js').module,
};

Fix perseus demo loading of extra widgets
Fix perseus demo loading of extra widgets

Summary: After my last commit, f8ce7339879495c2f0bc6b5623891d5436e13722, I
fixed the building of the perseus demo bundle, but loading
http://khan.github.io/perseus/ still didn't work! This time, it looked like
we're failing to load in the extra widgets webpack bundle. It looks like the
path for the bundle is wrong, because it's looking for it at `/build/*` but
since the page is at `/perseus/`, the correct path is `/perseus/build/*`.

The solution to this (I think?) is to change the path that webpack looks for
the bundle at, which is what I did.

Test Plan:
 - Run `make server`, visit http://localhost:9000/, see that the local version
   loads and works.
 - `make build/demo-perseus.js`
 - `cd ../ && python -m SimpleHTTPServer 8765`
 - Visit http://localhost:8765/perseus/
 - See that the demo loads and works.
 - *cross fingers*

Auditors: joshuan
