Skip to content

Commit c0aa2bb

Browse files
minho42NataliaTepluhina
authored andcommitted
Fix typos (vuejs#4241)
1 parent 246ae67 commit c0aa2bb

File tree

17 files changed

+22
-22
lines changed

17 files changed

+22
-22
lines changed

CHANGELOG.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -434,7 +434,7 @@ Most of the following new features and bugfixes also applies to v3.8.0
434434
#### Bug Fixes
435435

436436
* should not add polyfills from transform-runtime plugin ([#3730](https://github.com/vuejs/vue-cli/issues/3730)) ([b987969](https://github.com/vuejs/vue-cli/commit/b987969))
437-
* should not use abosulte polyfill paths when `absoluteRuntime` is on ([#3732](https://github.com/vuejs/vue-cli/issues/3732)) ([9bdff3b](https://github.com/vuejs/vue-cli/commit/9bdff3b)), closes [#3725](https://github.com/vuejs/vue-cli/issues/3725)
437+
* should not use absolute polyfill paths when `absoluteRuntime` is on ([#3732](https://github.com/vuejs/vue-cli/issues/3732)) ([9bdff3b](https://github.com/vuejs/vue-cli/commit/9bdff3b)), closes [#3725](https://github.com/vuejs/vue-cli/issues/3725)
438438

439439
## cli-plugin-babel
440440

@@ -2233,7 +2233,7 @@ and want to retain the previous behavior, you can configure webpack to use
22332233
`output.libraryExport: 'default'` in `vue.config.js`.
22342234
* **ui:** - `file-icon` for the configurations is removed
22352235
- Configuration objects `icon` option changed and is now working differently: you can either use a material icon code or a custom image (see Public static files in the UI Plugin docs).
2236-
- Task objects have a new `icon` option wich works exactly the same
2236+
- Task objects have a new `icon` option which works exactly the same
22372237
- By default, if no icon is provided for either the config or the task, the corresponding vue-cli plugin logo will be used instead (if any).
22382238
* jest is upgraded to 23.1.0 with minor breaking changes
22392239
but should not affect normal test cases

docs/dev-guide/generator-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The version string for the **global** `@vue/cli` version that is invoking the pl
1717
While api.version can be useful in general, it's sometimes nice to just declare your version.
1818
This API exposes a simple way to do that.
1919

20-
Nothing happens if the provided version is satified. Otherwise, an error will be thrown.
20+
Nothing happens if the provided version is satisfied. Otherwise, an error will be thrown.
2121

2222

2323
## cliServiceVersion
@@ -36,7 +36,7 @@ The version string for the **project local** `@vue/cli-service` version that is
3636

3737
This API exposes a simple way to declare the required project local `@vue/cli-service` version.
3838

39-
Nothing happens if the provided version is satified. Otherwise, an error will be thrown.
39+
Nothing happens if the provided version is satisfied. Otherwise, an error will be thrown.
4040

4141

4242
## resolve

docs/dev-guide/plugin-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The version string for the `@vue/cli-service` version that is loading the plugin
1717
While api.version can be useful in general, it's sometimes nice to just declare your version.
1818
This API exposes a simple way to do that.
1919

20-
Nothing happens if the provided version is satified. Otherwise, an error will be thrown.
20+
Nothing happens if the provided version is satisfied. Otherwise, an error will be thrown.
2121

2222
## getCwd
2323

docs/dev-guide/plugin-dev.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -430,7 +430,7 @@ This is because the command's expected mode needs to be known before loading env
430430

431431
Prompts are required to handle user choices when creating a new project or adding a new plugin to the existing one. All prompts logic is stored inside the `prompts.js` file. The prompts are presented using [inquirer](https://github.com/SBoudrias/Inquirer.js) under the hood.
432432

433-
When user initialize the plugin by calling `vue invoke`, if the plugin contains a `prompts.js` in its root directory, it will be used during invocation. The file should export an array of [Questions](https://github.com/SBoudrias/Inquirer.js#question) that will be handled by Inquirer.js.
433+
When user initialize the plugin by calling `vue invoke`, if the plugin contains a `prompts.js` in its root directory, it will be used during invocation. The file should export an array of [Questions](https://github.com/SBoudrias/Inquirer.js#question) that will be handled by Inquirer.js.
434434

435435
You should export directly array of questions, or export function that return those.
436436

@@ -445,7 +445,7 @@ module.exports = [
445445
message: 'The locale of project localization.',
446446
validate: input => !!input,
447447
default: 'en'
448-
},
448+
},
449449
// ...
450450
]
451451
```
@@ -466,7 +466,7 @@ module.exports = pkg => {
466466
}
467467
]
468468

469-
// add dynamically propmpt
469+
// add dynamically prompt
470470
if ('@vue/cli-plugin-eslint' in (pkg.devDependencies || {})) {
471471
prompts.push({
472472
type: 'confirm',

docs/guide/mode-and-env.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ vue-cli-service build --mode development
1616

1717
When running `vue-cli-service`, environment variables are loaded from all [corresponding files](#environment-variables). If they don't contain a `NODE_ENV` variable, it will be set accordingly. For example, `NODE_ENV` will be set to `"production"` in production mode, `"test"` in test mode, and defaults to `"development"` otherwise.
1818

19-
Then `NODE_ENV` will determine the primary mode your app is runnning in - development, production or test - and consequently, what kind of webpack config will be created.
19+
Then `NODE_ENV` will determine the primary mode your app is running in - development, production or test - and consequently, what kind of webpack config will be created.
2020

2121
With `NODE_ENV` set to "test" for example, Vue CLI creates a webpack config that is intended to be used and optimized for unit tests. It doesn't process images and other assets that are unnecessary for unit tests.
2222

docs/zh/guide/mode-and-env.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ VUE_APP_TITLE=My App (staging)
7676
console.log(process.env.VUE_APP_SECRET)
7777
```
7878

79-
在构建过程中,`process.env.VUE_APP_SECRET` 将会被相应的值所取代。在 `VUE_APP_SECRET=secret` 的情况下,它会被替换为 `"sercet"`
79+
在构建过程中,`process.env.VUE_APP_SECRET` 将会被相应的值所取代。在 `VUE_APP_SECRET=secret` 的情况下,它会被替换为 `"secret"`
8080

8181
除了 `VUE_APP_*` 变量之外,在你的应用代码中始终可用的还有两个特殊的变量:
8282

packages/@vue/babel-preset-app/index.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ module.exports = (context, options = {}) => {
6060
// Undocumented option of @babel/plugin-transform-runtime.
6161
// When enabled, an absolute path is used when importing a runtime helper atfer tranforming.
6262
// This ensures the transpiled file always use the runtime version required in this package.
63-
// However, this may cause hash inconsitency if the project is moved to another directory.
63+
// However, this may cause hash inconsistency if the project is moved to another directory.
6464
// So here we allow user to explicit disable this option if hash consistency is a requirement
6565
// and the runtime version is sure to be correct.
6666
absoluteRuntime = runtimePath

packages/@vue/cli-plugin-e2e-nightwatch/index.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ module.exports = (api, options) => {
66
'--url': 'run e2e tests against given url instead of auto-starting dev server',
77
'--config': 'use custom nightwatch config file (overrides internals)',
88
'-e, --env': 'specify comma-delimited browser envs to run in (default: chrome)',
9-
'-t, --test': 'sepcify a test to run by name',
9+
'-t, --test': 'specify a test to run by name',
1010
'-f, --filter': 'glob to filter tests by filename'
1111
},
1212
details:

packages/@vue/cli-plugin-eslint/lint.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ module.exports = function lint (args = {}, api) {
4242
// code style consistent with user's selected eslint config.
4343
// Though, if users provided their own `.eslintignore` file, we don't want to
4444
// add our own customized ignore pattern here (in eslint, ignorePattern is
45-
// an addition to eslintignore, i.e. it can't be overriden by user),
45+
// an addition to eslintignore, i.e. it can't be overridden by user),
4646
// following the principle of least astonishment.
4747
config.ignorePattern = [
4848
'!.*.js',

packages/@vue/cli-service/__tests__/css.spec.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ test('css.extract', () => {
129129
}, 'production')
130130
LANGS.forEach(lang => {
131131
const loader = lang === 'css' ? [] : LOADERS[lang]
132-
// if postcss config is present, two postcss-loaders will be used becasue it
132+
// if postcss config is present, two postcss-loaders will be used because it
133133
// does not support mixing config files with loader options.
134134
expect(findLoaders(config2, lang)).toEqual(['vue-style', 'css', 'postcss', 'postcss'].concat(loader))
135135
expect(findOptions(config2, lang, 'css').importLoaders).toBe(3)

0 commit comments

Comments
 (0)