Skip to content

docs: remove futureEmitAssets #5678

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 11, 2021
Merged

docs: remove futureEmitAssets #5678

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 0 additions & 17 deletions src/content/configuration/output.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -629,23 +629,6 @@ type ModulePathData = {

T> In some contexts properties will use JavaScript code expressions instead of raw values. In these cases, the `WithLength` variant is available and should be used instead of slicing the original value.

## output.futureEmitAssets

`boolean = false`

Tells webpack to use the future version of asset emitting logic, which allows freeing memory of assets after emitting. It could break plugins that assume that assets are still readable after they were emitted.

W> `output.futureEmitAssets` option will be removed in webpack v5.0.0 and this behaviour will become the new default.

```javascript
module.exports = {
//...
output: {
futureEmitAssets: true,
},
};
```

## output.globalObject

`string = 'window'`
Expand Down