Skip to content

docs: update new package name #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions packages/typescript-eslint-parser/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ An ESLint custom parser which leverages [TypeScript ESTree](https://github.com/t
## Installation:

```sh
npm install --save-dev typescript-eslint-parser
npm install --save-dev @typescript-eslint/parser
```

## Usage
Expand All @@ -14,7 +14,7 @@ In your ESLint configuration file, set the `parser` property:

```json
{
"parser": "typescript-eslint-parser"
"parser": "@typescript-eslint/parser"
}
```

Expand Down Expand Up @@ -44,7 +44,7 @@ The following additional configuration options are available by specifying them

```json
{
"parser": "typescript-eslint-parser",
"parser": "@typescript-eslint/parser",
"parserOptions": {
"jsx": true,
"useJSXTextNode": true
Expand All @@ -68,7 +68,7 @@ Please check the current list of open and known issues and ensure the issue has

- ESLint Version
- TypeScript version
- The `typescript-eslint-parser` version
- The `@typescript-eslint/parser` version
- ESLint config or rules and plugins currently enabled

## Integration Tests
Expand All @@ -95,7 +95,7 @@ npm run kill-integration-test-containers

## Contributing

Issues and pull requests will be triaged and responded to as quickly as possible. We operate under the [ESLint Contributor Guidelines](http://eslint.org/docs/developer-guide/contributing), so please be sure to read them before contributing. If you're not sure where to dig in, check out the [issues](https://github.com/eslint/typescript-eslint-parser/issues).
Issues and pull requests will be triaged and responded to as quickly as possible. We operate under the [ESLint Contributor Guidelines](http://eslint.org/docs/developer-guide/contributing), so please be sure to read them before contributing. If you're not sure where to dig in, check out the [issues](https://github.com/typescript-eslint/typescript-eslint/issues).

## Build Commands

Expand Down