git.iko.soy/bridge
on bd2a4fd help sign in
bridge/config/webpackDevServer.config.js
104 lines 5.6 kB history raw
1'use strict';
3const errorOverlayMiddleware = require('react-dev-utils/errorOverlayMiddleware');
4const evalSourceMapMiddleware = require('react-dev-utils/evalSourceMapMiddleware');
5const noopServiceWorkerMiddleware = require('react-dev-utils/noopServiceWorkerMiddleware');
6const ignoredFiles = require('react-dev-utils/ignoredFiles');
7const paths = require('./paths');
8const fs = require('fs');
10const protocol = process.env.HTTPS === 'true' ? 'https' : 'http';
11const host = process.env.HOST || '0.0.0.0';
13module.exports = function(proxy, allowedHost) {
14 return {
15 // WebpackDevServer 2.4.3 introduced a security fix that prevents remote
16 // websites from potentially accessing local content through DNS rebinding:
17 // https://github.com/webpack/webpack-dev-server/issues/887
18 // https://medium.com/webpack/webpack-dev-server-middleware-security-issues-1489d950874a
19 // However, it made several existing use cases such as development in cloud
20 // environment or subdomains in development significantly more complicated:
21 // https://github.com/facebook/create-react-app/issues/2271
22 // https://github.com/facebook/create-react-app/issues/2233
23 // While we're investigating better solutions, for now we will take a
24 // compromise. Since our WDS configuration only serves files in the `public`
25 // folder we won't consider accessing them a vulnerability. However, if you
26 // use the `proxy` feature, it gets more dangerous because it can expose
27 // remote code execution vulnerabilities in backends like Django and Rails.
28 // So we will disable the host check normally, but enable it if you have
29 // specified the `proxy` setting. Finally, we let you override it if you
30 // really know what you're doing with a special environment variable.
31 disableHostCheck:
32 !proxy || process.env.DANGEROUSLY_DISABLE_HOST_CHECK === 'true',
33 // Enable gzip compression of generated files.
34 compress: true,
35 // Silence WebpackDevServer's own logs since they're generally not useful.
36 // It will still show compile warnings and errors with this setting.
37 clientLogLevel: 'none',
38 // By default WebpackDevServer serves physical files from current directory
39 // in addition to all the virtual build products that it serves from memory.
40 // This is confusing because those files won’t automatically be available in
41 // production build folder unless we copy them. However, copying the whole
42 // project directory is dangerous because we may expose sensitive files.
43 // Instead, we establish a convention that only files in `public` directory
44 // get served. Our build script will copy `public` into the `build` folder.
45 // In `index.html`, you can get URL of `public` folder with %PUBLIC_URL%:
46 // <link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico">
47 // In JavaScript code, you can access it with `process.env.PUBLIC_URL`.
48 // Note that we only recommend to use `public` folder as an escape hatch
49 // for files like `favicon.ico`, `manifest.json`, and libraries that are
50 // for some reason broken when imported through Webpack. If you just want to
51 // use an image, put it in `src` and `import` it from JavaScript instead.
52 contentBase: paths.appPublic,
53 // By default files from `contentBase` will not trigger a page reload.
54 watchContentBase: true,
55 // Enable hot reloading server. It will provide /sockjs-node/ endpoint
56 // for the WebpackDevServer client so it can learn when the files were
57 // updated. The WebpackDevServer client is included as an entry point
58 // in the Webpack development configuration. Note that only changes
59 // to CSS are currently hot reloaded. JS changes will refresh the browser.
60 hot: true,
61 // It is important to tell WebpackDevServer to use the same "root" path
62 // as we specified in the config. In development, we always serve from /.
63 publicPath: '/',
64 // WebpackDevServer is noisy by default so we emit custom message instead
65 // by listening to the compiler events with `compiler.hooks[...].tap` calls above.
66 quiet: true,
67 // Reportedly, this avoids CPU overload on some systems.
68 // https://github.com/facebook/create-react-app/issues/293
69 // src/node_modules is not ignored to support absolute imports
70 // https://github.com/facebook/create-react-app/issues/1065
71 watchOptions: {
72 ignored: ignoredFiles(paths.appSrc),
73 },
74 // Enable HTTPS if the HTTPS environment variable is set to 'true'
75 https: protocol === 'https',
76 host,
77 overlay: false,
78 historyApiFallback: {
79 // Paths with dots should still use the history fallback.
80 // See https://github.com/facebook/create-react-app/issues/387.
81 disableDotRule: true,
82 },
83 public: allowedHost,
84 proxy,
85 before(app, server) {
86 if (fs.existsSync(paths.proxySetup)) {
87 // This registers user provided middleware for proxy reasons
88 require(paths.proxySetup)(app);
89 }
91 // This lets us fetch source contents from webpack for the error overlay
92 app.use(evalSourceMapMiddleware(server));
93 // This lets us open files from the runtime error overlay.
94 app.use(errorOverlayMiddleware());
96 // This service worker file is effectively a 'no-op' that will reset any
97 // previous service worker registered for the same host:port combination.
98 // We do this in development to avoid hitting the production cache if
99 // it used the same host and port.
100 // https://github.com/facebook/create-react-app/issues/2272#issuecomment-302832432
101 app.use(noopServiceWorkerMiddleware());
102 },
103 };
104};