docs: fix formatting in workspace config and add helpful info for universal (#31399)
PR Close #31399
This commit is contained in:
parent
e30f494a39
commit
4b05ebc804
|
@ -273,10 +273,10 @@ For example, the following object values create and name a bundle that contains
|
|||
<code-example format="." language="json" linenums="false">
|
||||
|
||||
"styles": [
|
||||
{"input": "src/external-module/styles.scss", "inject": false, "bundleName: "external-module"}
|
||||
]
|
||||
"scripts": [{
|
||||
"input": "src/external-module/main.ts", "inject": false, "bundleName: "external-module"}
|
||||
{ "input": "src/external-module/styles.scss", "inject": false, "bundleName": "external-module" }
|
||||
],
|
||||
"scripts": [
|
||||
{ "input": "src/external-module/main.js", "inject": false, "bundleName": "external-module" }
|
||||
]
|
||||
|
||||
</code-example>
|
||||
|
@ -288,9 +288,9 @@ You can mix simple and complex file references for styles and scripts.
|
|||
"styles": [
|
||||
"src/styles.css",
|
||||
"src/more-styles.css",
|
||||
{ "input": "src/lazy-style.scss", "lazy": true },
|
||||
{ "input": "src/lazy-style.scss", "inject": false },
|
||||
{ "input": "src/pre-rename-style.scss", "bundleName": "renamed-style" },
|
||||
],
|
||||
]
|
||||
|
||||
</code-example>
|
||||
|
||||
|
@ -302,11 +302,15 @@ In Sass and Stylus you can make use of the `includePaths` functionality for both
|
|||
|
||||
To add paths, use the `stylePreprocessorOptions` option:
|
||||
|
||||
<code-example format="." language="json" linenums="false">
|
||||
|
||||
"stylePreprocessorOptions": {
|
||||
"includePaths": [
|
||||
"src/style-paths"
|
||||
]
|
||||
},
|
||||
}
|
||||
|
||||
</code-example>
|
||||
|
||||
Files in that folder, such as `src/style-paths/_variables.scss`, can be imported from anywhere in your project without the need for a relative path:
|
||||
|
||||
|
@ -348,10 +352,13 @@ For example:
|
|||
|
||||
</code-example>
|
||||
|
||||
<div class="alert is-helpful>
|
||||
<div class="alert is-helpful">
|
||||
|
||||
When using hidden source maps, source maps will not be referenced in the bundle.
|
||||
These are useful if you only want source maps to map error stack traces in error reporting tools,
|
||||
but don't want to expose your source maps in the browser developer tools.
|
||||
|
||||
For [Universal](guide/glossary#universal), you can reduce the code rendered in the HTML page by
|
||||
setting styles optimization to `true` and styles source maps to `false`.
|
||||
|
||||
</div>
|
Loading…
Reference in New Issue