Skip to content

Commit

Permalink
Fix typos
Browse files Browse the repository at this point in the history
  • Loading branch information
not-an-aardvark committed Feb 19, 2019
1 parent 49ad752 commit cac06a9
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion docs/developer-guide/shareable-configs.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ You should declare your dependency on ESLint in `package.json` using the [peerDe
}
```

If your shareable config depends on a plugin, you should also specify it as a `peerDependency` (plugins are be loaded relative to the end user's project, so the end user is required to install the plugins they need). However, if your shareable config depends on a third-party parser or another shareable config, you can specify these packages as `dependencies`.
If your shareable config depends on a plugin, you should also specify it as a `peerDependency` (plugins will be loaded relative to the end user's project, so the end user is required to install the plugins they need). However, if your shareable config depends on a third-party parser or another shareable config, you can specify these packages as `dependencies`.

You can also test your shareable config on your computer before publishing by linking your module globally. Type:

Expand Down
2 changes: 1 addition & 1 deletion docs/user-guide/configuring.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ Setting parser options helps ESLint determine what is a parsing error. All langu

By default, ESLint uses [Espree](https://github.com/eslint/espree) as its parser. You can optionally specify that a different parser should be used in your configuration file so long as the parser meets the following requirements:

1. It must be a Node module loadable from the config file where it appears. Usually, this means you should install the parser package separately from npm.
1. It must be a Node module loadable from the config file where it appears. Usually, this means you should install the parser package separately using npm.
1. It must conform to the [parser interface](/docs/developer-guide/working-with-plugins.md#working-with-custom-parsers).

Note that even with these compatibilities, there are no guarantees that an external parser will work correctly with ESLint and ESLint will not fix bugs related to incompatibilities with other parsers.
Expand Down
2 changes: 1 addition & 1 deletion lib/config/config-initializer.js
Original file line number Diff line number Diff line change
Expand Up @@ -327,7 +327,7 @@ function getConfigForStyleGuide(guide) {
}

/**
* Get the version ESLint currently being used.
* Get the version of ESLint currently being used.
* @returns {string|null} The version. If ESLint was not found, returns null.
*/
function getESLintVersion() {
Expand Down
2 changes: 1 addition & 1 deletion tests/lib/config/config-file.js
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ describe("ConfigFile", () => {
}, /Failed to resolve parser 'nonexistent-parser' declared in '[\w-/.:\\]+'.\nReferenced from: \/whatever/);
});

it("should fall back to default parser when a config called 'espree' is not found", () => {
it("should fall back to default parser when a parser called 'espree' is not found", () => {
assert.deepStrictEqual(
ConfigFile.loadObject({ parser: "espree" }, configContext, "/", "configName"),
{ parser: require.resolve("espree") }
Expand Down

0 comments on commit cac06a9

Please sign in to comment.