Fix typos

CHANGELOG.md

@@ -434,7 +434,7 @@ Most of the following new features and bugfixes also applies to v3.8.0
 #### Bug Fixes
 
 * 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))
-* 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)
+* 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)
 
 ## cli-plugin-babel
 
@@ -2233,7 +2233,7 @@ and want to retain the previous behavior, you can configure webpack to use
 `output.libraryExport: 'default'` in `vue.config.js`.
 * **ui:** - `file-icon` for the configurations is removed
 - 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).
-- Task objects have a new `icon` option wich works exactly the same
+- Task objects have a new `icon` option which works exactly the same
 - 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).
 * jest is upgraded to 23.1.0 with minor breaking changes
 but should not affect normal test cases

docs/dev-guide/generator-api.md

@@ -17,7 +17,7 @@ The version string for the **global** `@vue/cli` version that is invoking the pl
   While api.version can be useful in general, it's sometimes nice to just declare your version.
   This API exposes a simple way to do that.
 
-  Nothing happens if the provided version is satified. Otherwise, an error will be thrown.
+  Nothing happens if the provided version is satisfied. Otherwise, an error will be thrown.
 
 
 ## cliServiceVersion
@@ -36,7 +36,7 @@ The version string for the **project local** `@vue/cli-service` version that is
 
   This API exposes a simple way to declare the required project local `@vue/cli-service` version.
 
-  Nothing happens if the provided version is satified. Otherwise, an error will be thrown.
+  Nothing happens if the provided version is satisfied. Otherwise, an error will be thrown.
 
 
 ## resolve

docs/dev-guide/plugin-api.md

@@ -17,7 +17,7 @@ The version string for the `@vue/cli-service` version that is loading the plugin
   While api.version can be useful in general, it's sometimes nice to just declare your version.
   This API exposes a simple way to do that.
 
-  Nothing happens if the provided version is satified. Otherwise, an error will be thrown.
+  Nothing happens if the provided version is satisfied. Otherwise, an error will be thrown.
 
 ## getCwd
 

docs/dev-guide/plugin-dev.md

@@ -430,7 +430,7 @@ This is because the command's expected mode needs to be known before loading env
 
 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.
 
-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. 
+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.
 
 You should export directly array of questions, or export function that return those.
 
@@ -445,7 +445,7 @@ module.exports = [
     message: 'The locale of project localization.',
     validate: input => !!input,
     default: 'en'
-  }, 
+  },
   // ...
 ]
 ```
@@ -466,7 +466,7 @@ module.exports = pkg => {
     }
   ]
 
-  // add dynamically propmpt
+  // add dynamically prompt
   if ('@vue/cli-plugin-eslint' in (pkg.devDependencies || {})) {
     prompts.push({
       type: 'confirm',

docs/guide/mode-and-env.md

@@ -16,7 +16,7 @@ vue-cli-service build --mode development
 
 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.
 
-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.
+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.
 
 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.
 

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

@@ -76,7 +76,7 @@ VUE_APP_TITLE=My App (staging)
 console.log(process.env.VUE_APP_SECRET)
 ```
 
-在构建过程中，`process.env.VUE_APP_SECRET` 将会被相应的值所取代。在 `VUE_APP_SECRET=secret` 的情况下，它会被替换为 `"sercet"`。
+在构建过程中，`process.env.VUE_APP_SECRET` 将会被相应的值所取代。在 `VUE_APP_SECRET=secret` 的情况下，它会被替换为 `"secret"`。
 
 除了 `VUE_APP_*` 变量之外，在你的应用代码中始终可用的还有两个特殊的变量：
 

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

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

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

@@ -6,7 +6,7 @@ module.exports = (api, options) => {
       '--url': 'run e2e tests against given url instead of auto-starting dev server',
       '--config': 'use custom nightwatch config file (overrides internals)',
       '-e, --env': 'specify comma-delimited browser envs to run in (default: chrome)',
-      '-t, --test': 'sepcify a test to run by name',
+      '-t, --test': 'specify a test to run by name',
       '-f, --filter': 'glob to filter tests by filename'
     },
     details:

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

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

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

@@ -129,7 +129,7 @@ test('css.extract', () => {
   }, 'production')
   LANGS.forEach(lang => {
     const loader = lang === 'css' ? [] : LOADERS[lang]
-    // if postcss config is present, two postcss-loaders will be used becasue it
+    // if postcss config is present, two postcss-loaders will be used because it
     // does not support mixing config files with loader options.
     expect(findLoaders(config2, lang)).toEqual(['vue-style', 'css', 'postcss', 'postcss'].concat(loader))
     expect(findOptions(config2, lang, 'css').importLoaders).toBe(3)

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

@@ -88,7 +88,7 @@ test('no-unsafe-inline', async () => {
   const { stdout } = await project.run('vue-cli-service build --modern --no-unsafe-inline')
   expect(stdout).toMatch('Build complete.')
 
-  // should output a seperate safari-nomodule-fix bundle
+  // should output a separate safari-nomodule-fix bundle
   const files = await fs.readdir(path.join(project.dir, 'dist/js'))
   expect(files.some(f => /^safari-nomodule-fix\.js$/.test(f))).toBe(true)
 

packages/@vue/cli-service/lib/commands/serve.js

@@ -158,7 +158,7 @@ module.exports = (api, options) => {
         // launch editor support.
         // this works with vue-devtools & @vue/cli-overlay
         app.use('/__open-in-editor', launchEditorMiddleware(() => console.log(
-          `To specify an editor, sepcify the EDITOR env variable or ` +
+          `To specify an editor, specify the EDITOR env variable or ` +
           `add "editor" field to your Vue project config.\n`
         )))
         // allow other plugins to register middlewares, e.g. PWA

packages/@vue/cli-ui/apollo-server/api/PluginApi.js

@@ -203,7 +203,7 @@ class PluginApi {
   }
 
   /**
-   * Add a new task indepently from the scripts.
+   * Add a new task independently from the scripts.
    * The task will only appear in the UI.
    *
    * @param {object} options Task description

packages/@vue/cli-ui/apollo-server/connectors/plugins.js

@@ -244,7 +244,7 @@ function runPluginApi (id, pluginApi, context, filename = 'ui') {
       log(`${chalk.red('ERROR')} while loading plugin API: no function exported, for`, name, chalk.grey(pluginApi.cwd))
       logs.add({
         type: 'error',
-        message: `An error occured while loading ${name}: no function exported`
+        message: `An error occurred while loading ${name}: no function exported`
       })
     } else {
       pluginApi.pluginId = id
@@ -255,7 +255,7 @@ function runPluginApi (id, pluginApi, context, filename = 'ui') {
         log(`${chalk.red('ERROR')} while loading plugin API for ${name}:`, e)
         logs.add({
           type: 'error',
-          message: `An error occured while loading ${name}: ${e.message}`
+          message: `An error occurred while loading ${name}: ${e.message}`
         })
       }
       pluginApi.pluginId = null

packages/@vue/cli-ui/src/vue-apollo.js

@@ -56,7 +56,7 @@ export const apolloProvider = new VueApollo({
     })
   },
   errorHandler (error) {
-    console.log('%cAn error occured', 'background: red; color: white; padding: 4px; border-radius: 4px;font-weight: bold;')
+    console.log('%cAn error occurred', 'background: red; color: white; padding: 4px; border-radius: 4px;font-weight: bold;')
     console.log(error.message)
     if (error.graphQLErrors) {
       console.log(error.graphQLErrors)

packages/@vue/cli-ui/ui-defaults/widgets.js

@@ -75,7 +75,7 @@ module.exports = api => {
     maxCount: 1
   })
 
-  // Depdency updates
+  // Dependency updates
 
   setSharedData('dependency-updates.status', {
     status: 'loading',

packages/@vue/cli/lib/upgrade.js

@@ -193,7 +193,7 @@ async function getUpgradable (context) {
 }
 
 async function checkForUpdates (context) {
-  logWithSpinner('Gathering pacakage information...')
+  logWithSpinner('Gathering package information...')
   const upgradable = await getUpgradable(context)
   stopSpinner()