|
| 1 | +# 2025-10-02 ESLint TSC Meeting Notes |
| 2 | + |
| 3 | +## Transcript |
| 4 | + |
| 5 | +[`2025-10-02-transcript.md`](2025-10-02-transcript.md) |
| 6 | + |
| 7 | +## Attending |
| 8 | + |
| 9 | +- Nicholas C. Zakas (@nzakas) - TSC |
| 10 | +- Milos Djermanovic (@mdjermanovic) - TSC |
| 11 | +- Francesco Trotta (@fasttime) - TSC |
| 12 | + |
| 13 | +@nzakas moderated, and @sam3k took notes. |
| 14 | + |
| 15 | +## Topics |
| 16 | + |
| 17 | +### Statuses |
| 18 | + |
| 19 | +* **@nzakas:** Has been investigating the eslint.org bandwidth issues over the past couple of days. Wrote the "What's coming in v10" blog post and has been working on updating the types in eslint to use @eslint/core. |
| 20 | +* **@mdjermanovic:** Finished work on changes in eslint-scope and eslint regarding handling of global variables, and was reviewing PRs. |
| 21 | +* **@fasttime:** Was mostly busy reviewing PRs and issues. |
| 22 | + |
| 23 | +### Availability Next Two Weeks |
| 24 | + |
| 25 | +* **@nzakas:** Still 0.5-1 hours per weekday. |
| 26 | +* **@mdjermanovic:** Expects to work around 2 hours each day. |
| 27 | +* **@fasttime:** Should be available about 9 hours per week the next two weeks. |
| 28 | + |
| 29 | +### RFC Duty Update |
| 30 | + |
| 31 | +* This week: @nzakas |
| 32 | +* October 6: @mdjermanovic |
| 33 | +* October 13: @fasttime |
| 34 | + |
| 35 | +### eslint.org Bandwidth Issues |
| 36 | + |
| 37 | +**TSC Summary:** ESLint received an email from Netlify reporting that 50% of the monthly bandwidth allowance had been used early in October. Investigation revealed that bandwidth usage had jumped by more than 50x starting September 25th. Netlify's Elad Rosenheim identified a spike in requests from China targeting https://eslint.org/feed.xml with suspicious user agents (specifically Chrome 58). The problem was compounded by feed.xml being over 600kb because it included every blog post ever published on eslint.org. |
| 38 | + |
| 39 | +**Resolution:** The TSC implemented a two-part solution: |
| 40 | +1. Reduced feed.xml file size by limiting it to only the 10 most recent blog posts ([PR #795](https://github.com/eslint/eslint.org/pull/795)) |
| 41 | +2. Added a temporary firewall rule to block all traffic from China, with plans to replace it with a targeted Netlify Edge function that only blocks China from accessing feed.xml ([PR #796](https://github.com/eslint/eslint.org/pull/796)) |
| 42 | + |
| 43 | +The team noted they currently have ~350GB bandwidth remaining until October 19, which should cover normal usage. @mdjermanovic suggested it would be helpful to have notifications for bandwidth spikes, though @nzakas noted this feature isn't currently available from Netlify. @fasttime asked about viewing request analytics without contacting Netlify, but this capability also doesn't exist. |
| 44 | + |
| 45 | +### "Feedback Needed" Label Usage |
| 46 | + |
| 47 | +**TSC Summary:** @nzakas raised concerns that the "Feedback Needed" label has become a parking lot for most changes, including simple, straightforward issue requests ([example: eslint/eslint#20165](https://github.com/eslint/eslint/issues/20165)). This appears unnecessary when requests are low-risk and unlikely to face concerns from other team members. |
| 48 | + |
| 49 | +**TSC Question:** Should we reserve "Feedback Needed" for controversial, large, breaking, or risky changes, and allow TSC members to mark low-risk issues as accepted without requiring additional feedback? |
| 50 | + |
| 51 | +**Resolution:** The TSC agreed to reserve "Feedback Needed" for larger decisions that genuinely need team input. TSC members can now proactively mark smaller changes they agree with as "accepted" to avoid blocking straightforward improvements while waiting for consensus. |
| 52 | + |
| 53 | +### V10 Development Planning |
| 54 | + |
| 55 | +The TSC reviewed the [v10.0.0 project board](https://github.com/orgs/eslint/projects/6) and agreed to finalize the scope today, deciding that after this meeting no more features will be considered for v10 (anything else must wait for v11). |
| 56 | + |
| 57 | +#### [Change Request: Remove deprecated Node and renamed core rules](https://github.com/eslint/eslint/issues/20171) |
| 58 | + |
| 59 | +**TSC Summary:** While working on another issue, it was discovered that 19 rules have deprecation metadata with `availableUntil` set to null. Of these, 17 are safe to remove (deprecated in ESLint < 8). |
| 60 | + |
| 61 | +**TSC Question:** Should we remove these deprecated rules in v10 or defer to v11? |
| 62 | + |
| 63 | +**Resolution:** The TSC agreed to move this to v11. @nzakas expressed no urgency to remove deprecated rules, and all members agreed this can wait. All deprecated rules accumulated so far will be considered for removal in v11. |
| 64 | + |
| 65 | +#### [Change Request: Remove `nodejsScope` option of eslint-scope](https://github.com/eslint/js/issues/697) |
| 66 | + |
| 67 | +**TSC Summary:** There are currently two different ways to enable commonjs scope analysis in eslint-scope. This issue proposes removing the `nodejsScope` option to consolidate the approach. |
| 68 | + |
| 69 | +**TSC Question:** Should we remove the `nodejsScope` option from eslint-scope for v10? |
| 70 | + |
| 71 | +**Resolution:** The TSC unanimously agreed to remove `nodejsScope` from eslint-scope for v10. |
| 72 | + |
| 73 | +**Next Steps:** The TSC noted that changes to eslint-scope and espree need to be completed before considering a prerelease. They agreed to re-evaluate v10 prerelease readiness at the next TSC meeting. |
| 74 | + |
| 75 | +### September 2025 Contributor Pool |
| 76 | + |
| 77 | +The TSC reviewed the [September contributor pool report](https://github.com/eslint/tsc-meetings/blob/main/notes/2025/2025-10-01-contributor-pool.md) and adjusted the following payouts: |
| 78 | + |
| 79 | +| Contributor | PRs | Payout | |
| 80 | +|---------------|-----|--------| |
| 81 | +| Pixel998 | 17 | $800 | |
| 82 | +| jaymarvelz | 4 | $850 | |
| 83 | +| thecalamiity | 2 | $450 | |
| 84 | +| sethamus | 1 | $200 | |
| 85 | +| SwetaTanwar | 1 | $250 | |
| 86 | +| ntnyq | 1 | $100 | |
| 87 | +| Amnish04 | 1 | $600 | |
| 88 | +| TKDev7 | 1 | $300 | |
| 89 | + |
| 90 | +### Scheduled release for October 3rd, 2025 |
| 91 | + |
| 92 | +**Action Items:** |
| 93 | + |
| 94 | +- @fasttime will: |
| 95 | + - Release `@eslint/js` and `eslint` |
| 96 | +- @nzakas will: |
| 97 | + - Work with @fasttime and @mdjermanovic to review and publish the ["What's coming in ESLint v10.0.0" blog post](https://github.com/eslint/eslint.org/pull/792) alongside the release |
| 98 | + |
| 99 | +**Note:** @mdjermanovic left a suggestion for adding a paragraph about scope manager changes, but @nzakas noted that typescript-eslint is already aware of the change and there are no other known scope managers, so it may not need to be mentioned in the blog post. |
0 commit comments