Geen omschrijving

webpackDevServer.config.js 5.2KB

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