Build times very slow with NX 12

@soer7022 I don’t think we can solve this problem. I think as of now nx needs better ways to debug and profile the build process, because we just need to accept the fact that a lot of the JS build tools are kinda awful IMO. I suggest we add options to create a profile via the webpack ProfilingPlugin and use the SpeedMeasurePlugin to get a better overview about the build times.

@HaveF as kenptr pointed out you set the webpack config path in your workspace.json. Then you can use something like this:

const nxWebpack = require('@nrwl/react/plugins/webpack');
const SpeedMeasurePlugin = require('speed-measure-webpack-plugin');
const webpack = require('webpack');

const logConfig = false;
const profileWebpack = false;
const measureSpeed = true;

module.exports = (config, context) => {
  let newConfig = nxWebpack(config, context);

  if(measureSpeed) {
    const smp = new SpeedMeasurePlugin();
    newConfig = smp.wrap(newConfig);
  }

  if(profileWebpack) {
    const profilePlugin = new webpack.debug.ProfilingPlugin();
    newConfig.plugins.push(profilePlugin)
  }

  if(logConfig)
    console.log(JSON.stringify(newConfig.module, null, 4));

  return newConfig;
};

With profiling I found the error actually It seems that ‘babel-plugin-transform-typescript-metadata’ is the problem here and takes 30 minutes to detect that my 5mb client.ts file is too large to process. I disabled ‘emitDecoratorMetadata’, which is enabled by default, for now which works as a workaround.

Is there an option to use NX without Babel? Because I would prefer to keep out as much build tools written in pure JS as possible, because in general I think they are low quality and hard to debug.