Skip to content
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.

Sign up for GitHub

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

Jump to bottom

docs: fix typo in blog post #599

Closed
wants to merge 1 commit into from
Closed

docs: fix typo in blog post #599

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion src/content/blog/2024-07-05-whats-coming-next-for-eslint.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ In 2023, the [language plugins RFC](https://github.com/eslint/rfcs/blob/main/des
Here's what to expect going forward (with no specific timetable as everything is dependent upon contributor availability):

* **`@eslint/js`** - We will slowly move all of the JavaScript-related functionality into the `@eslint/js` package, including rules and documentation. We will reuse the existing [Espree repo](https://github.com/eslint/espree/issues/609) and convert it into a monorepo containing Espree, `eslint-scope`, `eslint-visitor-keys`, and all of the core JavaScript rules. This will allow us to deal with everything JavaScript-related in a single repo.
* **`@eslint/json`** - Our first language plugin will allow ESLint to lint JSON files natively. This plugin will contain the parsing logic and all of the related rules and documentation. Similar to `@eslint/json`, this will allow us to have a single repo to focus on JSON linting, further moving any language-specific functionality away from the core.
* **`@eslint/json`** - Our first language plugin will allow ESLint to lint JSON files natively. This plugin will contain the parsing logic and all of the related rules and documentation. Similar to `@eslint/js`, this will allow us to have a single repo to focus on JSON linting, further moving any language-specific functionality away from the core.
* **`@eslint/markdown`** - [`eslint-plugin-markdown`](https://github.com/eslint/eslint-plugin-markdown) will be renamed to `@eslint/markdown` to better align with the other packages. We'll add the ability to lint Markdown and Markdown-specific rules.

The current plan is to have these three official ESLint language plugins with the hopes that they serve as examples for the ecosystem to develop more language plugins.
Expand Down
Loading