forked from microsoft/FluidFramework
-
Notifications
You must be signed in to change notification settings - Fork 0
/
webpack.config.js
53 lines (50 loc) · 1.95 KB
/
webpack.config.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
/*!
* Copyright (c) Microsoft Corporation and contributors. All rights reserved.
* Licensed under the MIT License.
*/
const fluidRoute = require("@fluid-tools/webpack-fluid-loader");
const path = require("path");
const { merge } = require("webpack-merge");
module.exports = env => {
const isProduction = env && env.production;
return merge({
entry: {
main: "./src/index.ts"
},
resolve: {
extensions: [".ts", ".tsx", ".js"],
},
module: {
rules: [{
test: /\.tsx?$/,
loader: require.resolve("ts-loader")
},
{
test: /\.css$/,
use: [
require.resolve("style-loader"), // creates style nodes from JS strings
require.resolve("css-loader"), // translates CSS into CommonJS
]
}]
},
output: {
filename: "[name].bundle.js",
path: path.resolve(__dirname, "dist"),
library: "[name]",
// https://github.com/webpack/webpack/issues/5767
// https://github.com/webpack/webpack/issues/7939
devtoolNamespace: "fluid-example/multiview-container",
libraryTarget: "umd"
},
// This impacts which files are watched by the dev server (and likely by webpack if watch is true).
// This should be configurable under devServer.static.watch
// (see https://github.com/webpack/webpack-dev-server/blob/master/migration-v4.md) but that does not seem to work.
// The CLI options for disabling watching don't seem to work either, so this may be a symptom of using webpack4 with the newer webpack-cli and webpack-dev-server.
watchOptions: {
ignored: "**/node_modules/**",
}
}, isProduction
? require("./webpack.prod")
: require("./webpack.dev"),
fluidRoute.devServerConfig(__dirname, env));
};