Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow to disable some deprecations #14653

Merged
merged 3 commits into from Nov 5, 2021
Merged

allow to disable some deprecations #14653

merged 3 commits into from Nov 5, 2021

Conversation

sokra
Copy link
Member

@sokra sokra commented Nov 5, 2021

fixes #14580

What kind of change does this PR introduce?
feature

Did you add tests for your changes?
yes

Does this PR introduce a breaking change?
no

What needs to be documented once your changes are merged?
add experiments.backCompat: false (default in experiments.futureDefaults)
remove unused experiments.asset
enable experiments.topLevelAwait and experiments.asyncWebAssembly by default in experiments.futureDefaults

add `experiments.backCompat: false` (default in `experiments.futureDefaults`)
remove unused `experiments.asset`
enable `experiments.topLevelAwait` and `experiments.asyncWebAssembly` by default in `experiments.futureDefaults`
@webpack-bot
Copy link
Contributor

webpack-bot commented Nov 5, 2021

For maintainers only:

  • This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
  • This needs to be backported to webpack 4 (issue will be created when merged)

@webpack-bot
Copy link
Contributor

webpack-bot commented Nov 5, 2021

@sokra The most important CI builds failed. This way your PR can't be merged.

Please take a look at the CI results from azure (0 errors / 5 warnings) and appveyor (failure) and fix these issues.

@sokra sokra merged commit 122db57 into main Nov 5, 2021
38 of 39 checks passed
@sokra sokra deleted the feature/no-back-compat branch Nov 5, 2021
@webpack-bot
Copy link
Contributor

webpack-bot commented Nov 5, 2021

I've created an issue to document this in webpack/webpack.js.org.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Webpack 5 triggers a slow V8 concat path resulting in significant performance degradation in some scenarios
2 participants