webpackDevServer.config.js 7.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136
  1. 'use strict';
  2. const fs = require('fs');
  3. const errorOverlayMiddleware = require('react-dev-utils/errorOverlayMiddleware');
  4. const evalSourceMapMiddleware = require('react-dev-utils/evalSourceMapMiddleware');
  5. const noopServiceWorkerMiddleware = require('react-dev-utils/noopServiceWorkerMiddleware');
  6. const ignoredFiles = require('react-dev-utils/ignoredFiles');
  7. const redirectServedPath = require('react-dev-utils/redirectServedPathMiddleware');
  8. const paths = require('./paths');
  9. const getHttpsConfig = require('./getHttpsConfig');
  10. const host = process.env.HOST || '0.0.0.0';
  11. const sockHost = process.env.WDS_SOCKET_HOST;
  12. const sockPath = process.env.WDS_SOCKET_PATH; // default: '/sockjs-node'
  13. const sockPort = process.env.WDS_SOCKET_PORT;
  14. module.exports = function(proxy, allowedHost) {
  15. return {
  16. // WebpackDevServer 2.4.3 introduced a security fix that prevents remote
  17. // websites from potentially accessing local content through DNS rebinding:
  18. // https://github.com/webpack/webpack-dev-server/issues/887
  19. // https://medium.com/webpack/webpack-dev-server-middleware-security-issues-1489d950874a
  20. // However, it made several existing use cases such as development in cloud
  21. // environment or subdomains in development significantly more complicated:
  22. // https://github.com/facebook/create-react-app/issues/2271
  23. // https://github.com/facebook/create-react-app/issues/2233
  24. // While we're investigating better solutions, for now we will take a
  25. // compromise. Since our WDS configuration only serves files in the `public`
  26. // folder we won't consider accessing them a vulnerability. However, if you
  27. // use the `proxy` feature, it gets more dangerous because it can expose
  28. // remote code execution vulnerabilities in backends like Django and Rails.
  29. // So we will disable the host check normally, but enable it if you have
  30. // specified the `proxy` setting. Finally, we let you override it if you
  31. // really know what you're doing with a special environment variable.
  32. disableHostCheck: !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="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. contentBasePublicPath: paths.publicUrlOrPath,
  54. // By default files from `contentBase` will not trigger a page reload.
  55. watchContentBase: true,
  56. // Enable hot reloading server. It will provide WDS_SOCKET_PATH endpoint
  57. // for the WebpackDevServer client so it can learn when the files were
  58. // updated. The WebpackDevServer client is included as an entry point
  59. // in the webpack development configuration. Note that only changes
  60. // to CSS are currently hot reloaded. JS changes will refresh the browser.
  61. hot: true,
  62. // Use 'ws' instead of 'sockjs-node' on server since we're using native
  63. // websockets in `webpackHotDevClient`.
  64. transportMode: 'ws',
  65. // Prevent a WS client from getting injected as we're already including
  66. // `webpackHotDevClient`.
  67. injectClient: false,
  68. // Enable custom sockjs pathname for websocket connection to hot reloading server.
  69. // Enable custom sockjs hostname, pathname and port for websocket connection
  70. // to hot reloading server.
  71. sockHost,
  72. sockPath,
  73. sockPort,
  74. // It is important to tell WebpackDevServer to use the same "publicPath" path as
  75. // we specified in the webpack config. When homepage is '.', default to serving
  76. // from the root.
  77. // remove last slash so user can land on `/test` instead of `/test/`
  78. publicPath: paths.publicUrlOrPath.slice(0, -1),
  79. // WebpackDevServer is noisy by default so we emit custom message instead
  80. // by listening to the compiler events with `compiler.hooks[...].tap` calls above.
  81. quiet: true,
  82. // Reportedly, this avoids CPU overload on some systems.
  83. // https://github.com/facebook/create-react-app/issues/293
  84. // src/node_modules is not ignored to support absolute imports
  85. // https://github.com/facebook/create-react-app/issues/1065
  86. watchOptions: {
  87. ignored: ignoredFiles(paths.appSrc),
  88. },
  89. https: getHttpsConfig(),
  90. host,
  91. overlay: false,
  92. historyApiFallback: {
  93. // Paths with dots should still use the history fallback.
  94. // See https://github.com/facebook/create-react-app/issues/387.
  95. disableDotRule: true,
  96. index: paths.publicUrlOrPath,
  97. },
  98. public: allowedHost,
  99. // `proxy` is run between `before` and `after` `webpack-dev-server` hooks
  100. proxy: {
  101. '/aiSquare/openApi/uc/': {
  102. // '/api':匹配项
  103. target: 'http://uc.ai.zj.chinamobile.com:8183/', // 接口的域名 // secure: false,// 如果是https接口,需要配置这个参数
  104. changeOrigin: true, // 如果接口跨域,需要进行这个参数配置 // pathRewrite: {// 如果接口本身没有/api需要通过pathRewrite来重写了地址 // '^api': ''
  105. // }
  106. },
  107. },
  108. before(app, server) {
  109. // Keep `evalSourceMapMiddleware` and `errorOverlayMiddleware`
  110. // middlewares before `redirectServedPath` otherwise will not have any effect
  111. // This lets us fetch source contents from webpack for the error overlay
  112. app.use(evalSourceMapMiddleware(server));
  113. // This lets us open files from the runtime error overlay.
  114. app.use(errorOverlayMiddleware());
  115. if (fs.existsSync(paths.proxySetup)) {
  116. // This registers user provided middleware for proxy reasons
  117. require(paths.proxySetup)(app);
  118. }
  119. },
  120. after(app) {
  121. // Redirect to `PUBLIC_URL` or `homepage` from `package.json` if url not match
  122. app.use(redirectServedPath(paths.publicUrlOrPath));
  123. // This service worker file is effectively a 'no-op' that will reset any
  124. // previous service worker registered for the same host:port combination.
  125. // We do this in development to avoid hitting the production cache if
  126. // it used the same host and port.
  127. // https://github.com/facebook/create-react-app/issues/2272#issuecomment-302832432
  128. app.use(noopServiceWorkerMiddleware(paths.publicUrlOrPath));
  129. },
  130. };
  131. };