flushChunkNames() returning empty array with base reactQL setup about webpack-flush-chunks HOT 5 CLOSED

Will definitely look into it! It's the least I could do. Thanks again for your awesome work.

from webpack-flush-chunks.

Sorry to keep creating and closing issues.

This was fixed by ditching the webpack-node-externals using the whitelist options, and constructing the externals object myself.

from webpack-flush-chunks.

Not a problem...You know, i need to look into why webpack-node-externals is problematic. If you have time, it would be great to get some clues on why it doesn't work. no pressure.

from webpack-flush-chunks.

I'd really like to know why webpack-node-externals won't work.. I've tried to get it to work with react-universal-component and webpack-flush-chunks, but nothing works. I've got kinda complex externals, so your version of node-externals will not work unfortunately.

Any idea what could be causing the incompatibility with webpack-node-externals?

from webpack-flush-chunks.

After putting the babel plugin into my own application:

const babelOptions = {
    presets: ['react'],
    plugins: [
      'syntax-dynamic-import',
      'transform-object-rest-spread',
      // 'transform-es2015-destructuring',
      'transform-decorators-legacy',
      'transform-class-properties',
      'transform-es2015-classes',
      ['import', { libraryName: 'antd', style: true }],
      resolve(__dirname, 'universal-import'),
    ],
  };

The problem with webpack-node-externals disappeared and server works perfectly fine.

from webpack-flush-chunks.