Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit 51cb6bd

Browse files
xp44mmchenxsan
andauthored
docs: e. g. -> e.g. (#4157)
* e. g. -> e.g. * ignore * del.vs * revert .gitignore Co-authored-by: Sam Chen <chenxsan@gmail.com>
1 parent 1b13f7f commit 51cb6bd

File tree

6 files changed

+9
-9
lines changed

6 files changed

+9
-9
lines changed

‎src/content/api/loaders.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -390,7 +390,7 @@ loadModule(request: string, callback: function(err, source, sourceMap, module))
390390

391391
Resolves the given request to a module, applies all configured loaders and calls back with the generated source, the sourceMap and the module instance (usually an instance of [`NormalModule`](https://github.com/webpack/webpack/blob/master/lib/NormalModule.js)). Use this function if you need to know the source code of another module to generate the result.
392392

393-
`this.loadModule` in a loader context uses CommonJS resolve rules by default. Use `this.getResolve` with an appropriate `dependencyType`, e.g. `'esm'`, `'commonjs'` or a custom one before using a different semantic.
393+
`this.loadModule` in a loader context uses CommonJS resolve rules by default. Use `this.getResolve` with an appropriate `dependencyType`, e.g. `'esm'`, `'commonjs'` or a custom one before using a different semantic.
394394

395395

396396
### `this.resolve`

‎src/content/blog/2020-10-10-webpack-5-release.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ __MIGRATION__: Use the default export.
168168

169169
Even when using the default export, unused properties are dropped by the `optimization.usedExports` optimization and properties are mangled by the `optimization.mangleExports` optimization.
170170

171-
It's possible to specify a custom JSON parser in `Rule.parser.parse` to import JSON-like files (e.g. for toml, yaml, json5, etc.).
171+
It's possible to specify a custom JSON parser in `Rule.parser.parse` to import JSON-like files (e.g. for toml, yaml, json5, etc.).
172172

173173
### import.meta
174174

@@ -475,7 +475,7 @@ The `target` option now influences more things about the generated code than bef
475475
- Some loaders might change behavior based on that
476476

477477
For some of these things the choice between `"web"` and `"node"` is too rough and we need more information.
478-
Therefore we allow to specify the minimum version e.g. like `"node10.13"` and infer more properties about the target environment.
478+
Therefore we allow to specify the minimum version e.g. like `"node10.13"` and infer more properties about the target environment.
479479

480480
It's now also allowed to combined multiple targets with an array and webpack will determine the minimum properties of all targets. Using an array is also useful when using targets that doesn't give full information like `"web"` or `"node"` (without version number). E. g. `["web", "es2020"]` combines these two partial targets.
481481

@@ -735,7 +735,7 @@ __MIGRATION__: Upgrade to the latest Node.js version available.
735735
- `stats.chunkRelations` added: Show parent/children/sibling chunks
736736
- `stats.errorStack` added: Show webpack-internal stack trace of errors
737737
- `stats.preset` added: select a preset
738-
- `stats.relatedAssets` added: show assets that are related to other assets (e.g. SourceMaps)
738+
- `stats.relatedAssets` added: show assets that are related to other assets (e.g. SourceMaps)
739739
- `stats.warningsFilter` deprecated in favor of `ignoreWarnings`
740740
- `BannerPlugin.banner` signature changed
741741
- `data.basename` removed
@@ -803,7 +803,7 @@ __MIGRATION__: This can be implemented in the loader itself
803803

804804
`getResolve(options)` in the loader API will merge options in a different way, see `module.rules` `resolve`.
805805

806-
As webpack 5 differs between different issuing dependencies so it might make sense to pass a `dependencyType` as option (e.g. `"esm"`, `"commonjs"`, or others).
806+
As webpack 5 differs between different issuing dependencies so it might make sense to pass a `dependencyType` as option (e.g. `"esm"`, `"commonjs"`, or others).
807807

808808
## Major Internal Changes
809809

‎src/content/configuration/stats.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -957,7 +957,7 @@ module.exports = {
957957

958958
`boolean = true`
959959

960-
Display children of the chunk groups (e.g. prefetched, preloaded chunks and assets).
960+
Display children of the chunk groups (e.g. prefetched, preloaded chunks and assets).
961961

962962
```javascript
963963
module.exports = {

‎src/content/guides/code-splitting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ The [`dependOn` option](/configuration/entry-context/#dependencies) allows to sh
147147

148148
Using multiple entry points per page should be avoided when possible in favor of an entry point with multiple imports: `entry: { page: ['./analytics', './app'] }`. This results in a better optimization and consistent execution order when using `async` script tags.
149149

150-
T> Multiple entry points per page could be used in scenarios where HTML is generated in a dynamic matter, e.g. when components on page are unknown at compile-time and HTML page is composed dynamically depending on the data.
150+
T> Multiple entry points per page could be used in scenarios where HTML is generated in a dynamic matter, e.g. when components on page are unknown at compile-time and HTML page is composed dynamically depending on the data.
151151

152152
### `SplitChunksPlugin`
153153

‎src/content/guides/ecma-script-modules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ In addition to the module format, flagging modules as ESM also affect the resolv
8181

8282
Imports in ESM are resolved more stictly. Relative requests must include a filename and file extension.
8383

84-
T> Requests to packages e.g. `import "lodash"` are still supported.
84+
T> Requests to packages e.g. `import "lodash"` are still supported.
8585

8686
Only the "default" export can be imported from non-ESM. Named exports are not available.
8787

‎src/content/migrate/5.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ Need to support an older browser?
129129

130130
- By default, webpack will use your browserslist config to decide which code style to emit.
131131
- Without a browserslist it would emit ES6 style. You can use `target: ["web", "es5"]` to change it to ES5.
132-
- For Node.js, builds include the supported Node.js version in the `target` option and webpack will automatically figure out which syntax is supported, e.g. `target: 'node8.6'`.
132+
- For Node.js, builds include the supported Node.js version in the `target` option and webpack will automatically figure out which syntax is supported, e.g. `target: 'node8.6'`.
133133

134134
#### Cleanup the code
135135

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /