'use strict'

const path = require('path')
const webpack = require('webpack')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const CaseSensitivePathsPlugin = require('case-sensitive-paths-webpack-plugin')
// const InterpolateHtmlPlugin = require('react-dev-utils/InterpolateHtmlPlugin')
const WatchMissingNodeModulesPlugin = require('react-dev-utils/WatchMissingNodeModulesPlugin')
// const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')
// const SpeedMeasurePlugin = require('speed-measure-webpack-plugin')
// const HardSourceWebpackPlugin = require('hard-source-webpack-plugin')
// const AutoDllPlugin = require('autodll-webpack-plugin')
// const ModuleScopePlugin = require('react-dev-utils/ModuleScopePlugin')
// const ForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin')
// const TsConfigPathsPlugin = require('tsconfig-paths-webpack-plugin')
const getClientEnvironment = require('./env')
const paths = require('./paths')
const { alias } = require('./alias')

const graphlSchemaLoader = {
  test: /\.(graphql|gql)$/,
  // exclude: /node_modules/,
  include: paths.appSrc,
  loader: require.resolve('@skava/webpack-loader-graphql/loader.js'),
}

// Webpack uses `publicPath` to determine where the app is being served from.
// In development, we always serve from the root. This makes config easier.
const publicPath = '/'
// `publicUrl` is just like `publicPath`, but we will provide it to our app
// as %PUBLIC_URL% in `index.html` and `process.env.PUBLIC_URL` in JavaScript.
// Omit trailing slash as %PUBLIC_PATH%/xyz looks better than %PUBLIC_PATH%xyz.
const publicUrl = ''
// Get environment variables to inject into our app.
const env = getClientEnvironment(publicUrl)

/**
 * @todo code split on each entry point?
 *
 * @description
 *  This is the development configuration.
 *  It is focused on developer experience and fast rebuilds.
 *  The production configuration is different and lives in a separate file.
 *
 * @type {webpack.Configuration}
 */
const config = {
  mode: 'development',
  // You may want 'eval' instead if you prefer to see the compiled output in DevTools.
  // See the discussion in https://github.com/facebookincubator/create-react-app/issues/343.
  // devtool: 'cheap-module-source-map',
  // These are the "entry points" to our application.
  // This means they will be the "root" imports that are included in JS bundle.
  // The first two entry points enable "hot" CSS and auto-refreshes for JS.
  entry: [
    // @todo put this on a cdn?
    // We ship a few polyfills by default:
    require.resolve('./polyfills'),

    // Include an alternative client for WebpackDevServer. A client's job is to
    // connect to WebpackDevServer by a socket and get notified about changes.
    // When you save a file, the client will either apply hot updates (in case
    // of CSS changes), or refresh the page (in case of JS changes). When you
    // make a syntax error, this client will display a syntax error overlay.
    // Note: instead of the default WebpackDevServer client, we use a custom one
    // to bring better experience for Create React App users. You can replace
    // the line below with these two lines if you prefer the stock client:
    // require.resolve('webpack-dev-server/client') + '?/',
    // require.resolve('webpack/hot/dev-server'),
    require.resolve('react-dev-utils/webpackHotDevClient'),

    // Finally, this is your app's code:
    paths.appIndexJs,
    // We include the app code last so that if there is a runtime error during
    // initialization, it doesn't blow up the WebpackDevServer client, and
    // changing JS code would still trigger a refresh.
  ],
  output: {
    // Add /* filename */ comments to generated require()s in the output.
    /**
     * @todo perf https://webpack.js.org/guides/build-performance/#output-without-path-info
     */
    pathinfo: true,
    // This does not produce a real file. It's just the virtual path that is
    // served by WebpackDevServer in development. This is the JS bundle
    // containing code from all our entry points, and the Webpack runtime.
    filename: 'static/js/bundle.js',
    // There are also additional JS chunk files if you use code splitting.
    chunkFilename: 'static/js/[name].chunk.js',
    // This is the URL that app is served from. We use "/" in development.
    publicPath,
    // Point sourcemap entries to original disk location (format as URL on Windows)
    devtoolModuleFilenameTemplate: info =>
      path.resolve(info.absoluteResourcePath).replace(/\\/g, '/'),
  },
  resolve: {
    // This allows you to set a fallback for where Webpack should look for modules.
    // We placed these paths second because we want `node_modules` to "win"
    // if there are any conflicts. This matches Node resolution mechanism.
    // https://github.com/facebookincubator/create-react-app/issues/253
    modules: ['node_modules', paths.appNodeModules].concat(
      // It is guaranteed to exist because we tweak it in `env.js`
      process.env.NODE_PATH.split(path.delimiter).filter(Boolean)
    ),
    // These are the reasonable defaults supported by the Node ecosystem.
    // We also include JSX as a common component filename extension to support
    // some tools, although we do not recommend using it, see:
    // https://github.com/facebookincubator/create-react-app/issues/290
    // `web` extension prefixes have been added for better support
    // for React Native Web.
    // @see https://webpack.js.org/guides/build-performance/#resolving
    extensions: [
      // '.mjs',
      // '.web.ts',
      '.ts',
      // '.web.tsx',
      '.tsx',
      // '.web.js',
      '.js',
      '.json',
      // '.web.jsx',
      // '.jsx',
    ],
    alias: {
      ...alias,
      // Support React Native Web
      // https://www.smashingmagazine.com/2016/08/a-glimpse-into-the-future-with-react-native-for-web/
      // 'react-native': 'react-native-web',
    },
    plugins: [
      // Prevents users from importing files from outside of src/ (or node_modules/).
      // This often causes confusion because we only process files within src/ with babel.
      // To fix this, we prevent you from importing files out of src/ -- if you'd like to,
      // please link the files into your node_modules/ and let module-resolution kick in.
      // Make sure your source files are compiled, as they will not be processed in any way.
      // new ModuleScopePlugin(paths.appSrc, [paths.appPackageJson]),
      // new TsConfigPathsPlugin({ configFile: paths.appTsConfig }),
    ],
  },
  module: {
    strictExportPresence: true,
    rules: [
      // TODO: Disable require.ensure as it's not a standard language feature.
      // We are waiting for https://github.com/facebookincubator/create-react-app/issues/2176.
      // { parser: { requireEnsure: false } },
      {
        test: /\.(js|jsx|mjs)$/,
        loader: require.resolve('source-map-loader'),
        enforce: 'pre',
        include: paths.appSrc,
      },
      {
        // "oneOf" will traverse all following loaders until one will
        // match the requirements. When no loader matches it will fall
        // back to the "file" loader at the end of the loader list.
        oneOf: [
          // "url" loader works like "file" loader except that it embeds assets
          // smaller than specified limit in bytes as data URLs to avoid requests.
          // A missing `test` is equivalent to a match.
          // {
          //   test: [/\.bmp$/, /\.gif$/, /\.jpe?g$/, /\.png$/],
          //   loader: require.resolve('url-loader'),
          //   options: {
          //     limit: 10000,
          //     name: 'static/media/[name].[hash:8].[ext]',
          //   },
          // },

          /**
           * @see https://github.com/TypeStrong/ts-loader#allowtsinnodemodules-boolean-defaultfalse
           * @see https://webpack.js.org/guides/build-performance/#typescript-loader
           * @see https://github.com/TypeStrong/ts-loader#ignorediagnostics-number-default
           */
          {
            test: /\.(ts|tsx)$/,
            include: paths.appSrc,
            use: [
              /**
               * @todo this is adding 10-20 seconds!!!!!!!!!!
               * 20/50
               *
               * @see https://github.com/Microsoft/TypeScriptSamples/blob/master/react-flux-babel-karma/webpack.config.js
               * @see https://github.com/amireh/happypack/issues/32
               */
              {
                loader: require.resolve('babel-loader'),
                options: {
                  cacheDirectory: true,
                  // compact: true,
                  babelrc: false,
                  // sourceMaps: false,
                  plugins: [
                    // server side render styled-components
                    [
                      require.resolve('babel-plugin-styled-components'),
                      {
                        ssr: true,
                        displayName: true,
                        minify: false,
                        transpileTemplateLiterals: false,
                        // minify: true,
                        // transpileTemplateLiterals: true,
                        // fileName: false,
                        // transpileTemplateLiterals: false,
                        // moduleName: "other-library",
                      },
                    ],
                    // reactSyntax: '@babel/plugin-syntax-jsx',
                    // reactSelf: '@babel/plugin-transform-react-jsx-self',
                    // reactSource: '@babel/plugin-transform-react-jsx-source',
                    '@babel/plugin-syntax-object-rest-spread',
                    '@babel/plugin-syntax-dynamic-import',
                  ],
                },
              },

              {
                loader: require.resolve('ts-loader'),
                options: {
                  // disable type checker - we will use it in fork plugin
                  transpileOnly: true,
                  experimentalWatchApi: true,
                },
              },
            ],
          },

          graphlSchemaLoader,

          // "file" loader makes sure those assets get served by WebpackDevServer.
          // When you `import` an asset, you get its (virtual) filename.
          // In production, they would get copied to the `build` folder.
          // This loader doesn't use a "test" so it will catch all modules
          // that fall through the other loaders.
          // {
          //   // Exclude `js` files to keep "css" loader working as it injects
          //   // its runtime that would otherwise processed through "file" loader.
          //   // Also exclude `html` and `json` extensions so they get processed
          //   // by webpacks internal loaders.
          //   exclude: [/\.(js|jsx|mjs)$/, /\.html$/, /\.json$/],
          //   loader: require.resolve('file-loader'),
          //   options: {
          //     name: 'static/media/[name].[hash:8].[ext]',
          //   },
          // },
        ],
      },
      // ** STOP ** Are you adding a new loader?
      // Make sure to add the new loader(s) before the "file" loader.
    ],
  },
  plugins: [
    // @note this causes issues with importing the wrong versions
    // new HardSourceWebpackPlugin(),

    // Makes some environment variables available in index.html.
    // The public URL is available as %PUBLIC_URL% in index.html, e.g.:
    // <link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico">
    // In development, this will be an empty string.
    // new InterpolateHtmlPlugin(env.raw),
    // Generates an `index.html` file with the <script> injected.
    new HtmlWebpackPlugin({
      inject: true,
      template: paths.appHtml,
    }),

    // @todo does not work when we have a few
    // new AutoDllPlugin({
    //   // will inject the DLL bundles to index.html
    //   inject: true,
    //   filename: '[name].js',
    //   entry: {
    //     vendor: []
    //   },
    // }),

    // Add module names to factory functions so they appear in browser profiler.
    new webpack.NamedModulesPlugin(),
    // Makes some environment variables available to the JS code, for example:
    // if (process.env.NODE_ENV === 'development') { ... }. See `./env.js`.
    new webpack.EnvironmentPlugin(env.asEnv),
    new webpack.DefinePlugin(env.stringified),
    // This is necessary to emit hot updates (currently CSS only):
    new webpack.HotModuleReplacementPlugin(),

    // Watcher doesn't work well if you mistype casing in a path so we use
    // a plugin that prints an error when you attempt to do this.
    // See https://github.com/facebookincubator/create-react-app/issues/240
    new CaseSensitivePathsPlugin(),

    // If you require a missing module and then `npm install` it, you still have
    // to restart the development server for Webpack to discover it. This plugin
    // makes the discovery automatic so you don't have to restart.
    // See https://github.com/facebookincubator/create-react-app/issues/186
    new WatchMissingNodeModulesPlugin(paths.appNodeModules),

    // new BundleAnalyzerPlugin(),
    // new require('lodash-webpack-plugin')(),

    // Perform type checking and linting in a separate process to speed up compilation
    // new ForkTsCheckerWebpackPlugin({
    //   async: false,
    //   watch: paths.appSrc,
    //   tsconfig: paths.appTsConfig,
    //   tslint: paths.appTsLint,
    // }),
  ],
  // Some libraries import Node modules but don't use them in the browser.
  // Tell Webpack to provide empty mocks for them so importing them works.
  node: {
    dgram: 'empty',
    fs: 'empty',
    net: 'empty',
    tls: 'empty',
    child_process: 'empty',
  },
  // Turn off performance hints during development because we don't do any
  // splitting or minification in interest of speed. These warnings become
  // cumbersome.
  performance: {
    hints: false,
  },
}

// const smp = new SpeedMeasurePlugin()
// module.exports = smp.wrap(config)
module.exports = config