Investigate breaks in experiments for webpack on performance-benchmark.

[TheLarkInn]

1. Fork or clone: https://github.com/TheLarkInn/performance-compare
2. Add experments.futureDefaults & experiments.lazyCompilation to both babel and swc webpack configurations
3. Run the individual start command npm run start:webpack
4. Open the dev server link

Expected Output:

• webpack dev mode loads the page just like all the other benchmarks do

Actual Outcome:

• Console errors related to lazyCompilation
  

• Console errors related to futureDefaults
  

[TheLarkInn]

I believe since there isn't many integrations that this is caused by: https://github.com/pmmmwh/react-refresh-webpack-plugin

[alexander-akait]

@TheLarkInn Is it broken?

[TheLarkInn]

I think this plugin breaks when used with experiments.futureDefaults and experiments.lazyCompilation. We can reduce further if needed but the original repo should be enough to triage I think. cc @pmmmwh

[TheLarkInn]

My concern is that this is a very popular plugin for webpack+react users so we should prioritize futureproofing finding the bugs in the plugin for when we enable these future defaults and features.

[alexander-akait]

Yeah, agree

[hardfist]

@TheLarkInn @alexander-akait
I'm digging this issue to investigate how fast webpack rebuild can become, and find it's the experiments.css:true and node.global:warn cause the runtime error and warning.
this config works on my machine

module.exports = 
{
   node: {
    global: false,
  },
  experiments: {
    css:false,
    futureDefaults:true
  }
}

related MR web-infra-dev/performance-compare#3

the performance gain is shown in the following

• before
  

• after
  

I'm wondering are there any configuration could improve rebuild performance of webpack, the problems we met in rspack when following webpack's rebuild strategy is that it seems the rebuild cost is linear to project's scale (related to module number and chunk number), so we take another approach like parcel's parcel-bundler/parcel#6047 which is faster in some normal edit case.

[webpack-bot]

This issue had no activity for at least three months.

It's subject to automatic issue closing if there is no activity in the next 15 days.

[pmmmwh]

Bump - I'll try to investigate this soon and hopefully we can figure out what's wrong

[alexander-akait]

bump

[hardfist]

@alexander-akait I investigated it before, it's not related to react-refresh-webpack-plugin, it's caused by futureDefault enable experiments.css by default which conflicts with style-loader, so disable experiments.css could solve this

[alexander-akait]

@hardfist oh, thank you, I think we need to send a fix there

[webpack-bot]

Issue was closed because of inactivity.

If you think this is still a valid issue, please file a new issue with additional information.