b

    Brandon Saunders

    2 years ago
    does anyone here know why splitChunks in the webpack definition on a multiplatform project that targets JS would cause the output to no longer go to the distributions folder? If I add the following to my webpack config
    config.optimization.splitChunks = {
        minSize: <someNumber>,
        maxSize: <theSameNumber>
     };
    I get nothing in my distributions folder. If I remove it, the distributions folder gets created on build. Any ideas?
    if i just call the assemble task that does generate the distributions folder
    for context, this splits up the resulting js based on size, resulting in file outputs of the format 1.js, 2.js, 3.js until all of the code that would originally go in main is accounted for
    andylamax

    andylamax

    2 years ago
    I ddn't know about this. Thank your for sharing this, though I know the problem is not solved still
    b

    Brandon Saunders

    2 years ago
    aha... we may have a piece of this puzzle. It seems jsBrowserProductionWebpack is sometimes skipped when splitChunks is used. Perhaps the detection logic to determine if this task is necessary expects a certain webpack configuration?