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

docs: Add 2024-01-25 meeting notes #482

Merged
merged 1 commit into from
Jan 29, 2024
Merged

docs: Add 2024-01-25 meeting notes #482

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
55 changes: 55 additions & 0 deletions notes/2024/2024-01-25.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
# 2024-01-25 ESLint TSC Meeting Notes

## Transcript

[`2024-01-25-transcript.md`](2024-01-25-transcript.md)

## Attending

- Nicholas C. Zakas (@nzakas) - TSC
- Milos Djermanovic (@mdjermanovic) - TSC

@nzakas moderated, and @sam3k took notes.

## Topics

### [Rule Change: Change default for no-unused-var's caughtErrors option to "all"](https://github.com/eslint/eslint/issues/17974)

**TSC Summary:** This issue seeks to change the default value of caughtErrors on no-unused-vars to "all". It's currently "none".

**TSC Question:** Do we want to change this option's default value?

**Resolution:** we've agreed to change the default of caughtErrors to "all".

### [Request: backporting flat config bug fixes to v8](https://github.com/eslint/eslint/issues/17966)

**TSC Summary:** We've made several bug fixes to flat config in the v9 branch that aren't in the v8 branch, which makes it difficult for plugins to support both v8 and v9 at the same time. This issue requests backporting those changes into v8 and then doing one last release in v8. At the moment, we don't have a way to release from any branch other than main, and we generate other artifacts (docs, release notes, blog posts) that all assume on branch.

**TSC Question:** Do we want to backport flat config fixes into v8? If so, how can we go about this in the least disruptive way possible?

**Resolution:** we've decided to:

- Do a backport release for the flat config changes
- The backport v8.x release will happen prior to the final v9.0.0 release
- We've agreed to publish to the `latest` tag
- The branch should be named `v8.x`

_Pending technical investigation._

**Action Items:** @mdjermanovic will investigate.

### [v9.0.0](https://github.com/orgs/eslint/projects/4/views/2)

We are just waiting on a couple of issues for beta:

- [Rule Change: Change default for no-unused-var's caughtErrors option to "all"](https://github.com/eslint/eslint/issues/17974)
- [Change Request: Stricter rule test validation](https://github.com/eslint/eslint/issues/15104)
- [Bug: Incorrect code path analysis for return in try blocks with catch clause](https://github.com/eslint/eslint/issues/17579)

### Scheduled release for January 26th, 2024

**Action Items:** @mdjermanovic will release:

- `espree` v10.0.0
- `@eslint/js`
- `eslint` v9.0.0-alpha.2
Loading