Skip to content

docs(configuration): remove cssHeadDataCompression #7475

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 23, 2024
Merged

docs(configuration): remove cssHeadDataCompression #7475

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
18 changes: 5 additions & 13 deletions src/content/configuration/output.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -350,14 +350,6 @@ This option determines the name of CSS output files on disk. See [`output.filena

You **must not** specify an absolute path here. However, feel free to include folders separated by `'/'`. This specified path combines with the [`output.path`](#outputpath) value to pinpoint the location on the disk.

## output.cssHeadDataCompression

<Badge text="5.91.0+" />

`boolean`

This option determines whether to compress the metadata generated in the head tag of CSS files. This option defaults to `true` in `production` and `false` in `development` [mode](/configuration/mode/) respectively.

## output.devtoolFallbackModuleFilenameTemplate

`string` `function (info)`
Expand Down Expand Up @@ -420,7 +412,7 @@ If multiple modules would result in the same name, [`output.devtoolFallbackModul

This option determines the module's namespace used with the [`output.devtoolModuleFilenameTemplate`](#outputdevtoolmodulefilenametemplate). When not specified, it will default to the value of: [`output.uniqueName`](#outputuniquename). It's used to prevent source file path collisions in sourcemaps when loading multiple libraries built with webpack.

For example, if you have 2 libraries, with namespaces `library1` and `library2`, which both have a file `./src/index.js` (with potentially different contents), they will expose these files as `webpack://library1/./src/index.js` and `webpack://library2/./src/index.js`.
For example, if you have 2 libraries, with namespaces `library1` and `library2`, which both have a file `./src/index.js` (with potentially different contents), they will expose these files as `webpack://library1/./src/index.js` and `webpack://library2/./src/index.js`.

You can use template strings like `[name]` to dynamically generate namespaces based on the build context, providing additional flexibility.

Expand All @@ -430,10 +422,10 @@ You can use template strings like `[name]` to dynamically generate namespaces ba
module.exports = {
//...
output: {
filename: "[name]-bundle.js",
library: "library-[name]",
libraryTarget: "commonjs",
devtoolNamespace: "library-[name]" // Sets a unique namespace for each library
filename: '[name]-bundle.js',
library: 'library-[name]',
libraryTarget: 'commonjs',
devtoolNamespace: 'library-[name]', // Sets a unique namespace for each library
},
};
```
Expand Down