|
| 1 | +# 01/09/2025 ESLint TSC Meeting Transcript |
| 2 | + |
| 3 | +**mdjermanovic:** Hi! |
| 4 | + |
| 5 | +**fasttime:** Hi 👋 |
| 6 | + |
| 7 | +**nzakas:** Howdy! |
| 8 | + |
| 9 | +**nzakas:** Just pulling up the notes from our last meeting |
| 10 | + |
| 11 | +**nzakas:** That was on 2024-12-12 |
| 12 | + |
| 13 | +**nzakas:** Okay, so only followup item was for @fasttime to unflag the TS config functionality, which has been completed. |
| 14 | + |
| 15 | +**nzakas:** Let's get started with statuses. For me, I've been working on the `extends` RFC, the CSS plugin, and fixing the GitHub bot (which we'll discuss in a moment). |
| 16 | + |
| 17 | +**mdjermanovic:** I fixed a bug with suggestions in `@eslint/markdown` and updated docs site to use flat config format in rule examples. |
| 18 | + |
| 19 | +**fasttime:** I opened the RFC for multithread linting, unflagged TS config file support, worked to fix some issues with types in the rewrite repo, and I also opened a PR to partly automate the process of generating TSDoc comments in rule types https://github.com/eslint/eslint/pull/19276. |
| 20 | + |
| 21 | +**nzakas:** Let's reset RFC duty next: |
| 22 | +Next week: @nzakas |
| 23 | + |
| 24 | +**nzakas:** Jan 20: @mdjermanovic |
| 25 | + |
| 26 | +**nzakas:** Jan 27: @fasttime |
| 27 | + * 👍 @mdjermanovic, @fasttime |
| 28 | + |
| 29 | +**nzakas:** Looks like we don't have any issues flagged. I do have a couple items to discuss. |
| 30 | + |
| 31 | +**nzakas:** First, @mdjermanovic noticed that the GitHub bot was down earlier this week. |
| 32 | + |
| 33 | +**nzakas:** I investigated and found that we're still running on Node.js 16 and Octokit made some breaking changes in a minor release so the app just crashed. |
| 34 | + |
| 35 | +**nzakas:** I'm in the process of updating the bot to run on Node.js 22 right now. It's a painfully slow process that AI doesn't seem to be able to make much of a dent in, so I'm just making my way through each plugin. |
| 36 | + |
| 37 | +**nzakas:** Probably will have it done early next week. |
| 38 | + |
| 39 | +**mdjermanovic:** Don't we have `package-lock.json`? |
| 40 | + |
| 41 | +**nzakas:** We do, but Dokku doesn't seem to be honoring it. |
| 42 | + |
| 43 | +**mdjermanovic:** Oh, that's unfortunate |
| 44 | + |
| 45 | +**nzakas:** In any event, it looks like Octokit and Probot aren't getting very frequently updated anymore, so hopefully once this is fixed we'll be set for a while. |
| 46 | + * 👍 @mdjermanovic |
| 47 | + |
| 48 | +**nzakas:** I going to remove some of the old plugins that are in there that we don't have enabled to reduce the amount of work. |
| 49 | + |
| 50 | +**nzakas:** Next topic: Browser tests. |
| 51 | + |
| 52 | +**nzakas:** https://github.com/eslint/eslint/issues/19234 |
| 53 | + |
| 54 | +**nzakas:** We're at the point now where the browser tests always fail and are useless. I think we need to prioritize moving to a different tool. |
| 55 | + |
| 56 | +**fasttime:** I've looked into this, was considering using Cypress as an alternative to WebdriverIO (https://www.cypress.io/). It looks like it's got everything we need. |
| 57 | + |
| 58 | +**fasttime:** It's definitely more used then wdio, so hopefully it'll run with less troubles. |
| 59 | + |
| 60 | +**nzakas:** I'm all for anything that just works. 🙂 I'm not opposed to going back to Karma, too, as it seemed to just work even though it was old. |
| 61 | + |
| 62 | +**fasttime:** Why did we move away from Karma? I think it's because it's no longer maintained? |
| 63 | + |
| 64 | +**mdjermanovic:** Yes, that was the reason |
| 65 | + * 👍 @fasttime |
| 66 | + |
| 67 | +**fasttime:** I could look more into Cypress next week. |
| 68 | + * 👍 @nzakas, @mdjermanovic |
| 69 | + |
| 70 | +**nzakas:** Sounds good. I think if we spend the next two weeks getting infrastructure fixed (GitHub bot and browser tests) that will be a good way to kick off 2025. |
| 71 | + |
| 72 | +**nzakas:** Any other topics to discuss before Contributor Pool? |
| 73 | + |
| 74 | +**mdjermanovic:** Nothing in particular from my side for today |
| 75 | + |
| 76 | +**fasttime:** Nothing from my side as well. |
| 77 | + |
| 78 | +**nzakas:** Okay, let's discuss Contributor Pool: |
| 79 | + |
| 80 | +**nzakas:** https://github.com/issues?q=org%3Aeslint+label%3A%22contributor+pool%22+merged%3A2024-12-01..2024-12-31 |
| 81 | + |
| 82 | +**nzakas:** I'm thinking $250 for hildjj's three PRs to `eslint/json` |
| 83 | + * 👍 @mdjermanovic, @fasttime |
| 84 | + |
| 85 | +**nzakas:** Unsure about aryaemami59's PR. Thoughts? |
| 86 | + |
| 87 | +**fasttime:** Maybe $200 because it took a while to complete? |
| 88 | + * 👍 @nzakas, @mdjermanovic |
| 89 | + |
| 90 | +**nzakas:** And $100 for the rest? |
| 91 | + * 👍 @mdjermanovic, @fasttime |
| 92 | + |
| 93 | +**nzakas:** Okay, I'll let them know. |
| 94 | + |
| 95 | +**nzakas:** Let's talk about the release tomorrow |
| 96 | + |
| 97 | +**fasttime:** I have time. |
| 98 | + * 🙏 @nzakas |
| 99 | + |
| 100 | +**mdjermanovic:** Thanks! |
| 101 | + |
| 102 | +**fasttime:** Just `eslint/js` and `eslint` as it seems. |
| 103 | + |
| 104 | +**nzakas:** Looks like it |
| 105 | + |
| 106 | +**mdjermanovic:** Maybe also `eslint/rewrite` packages? https://github.com/eslint/rewrite/pull/139 |
| 107 | + * 👍 @nzakas |
| 108 | + |
| 109 | +**fasttime:** Ah yes. Maybe we can release those earlier tomorrow, so there's time to update the dependencies in eslint. |
| 110 | + * 👍 @nzakas, @mdjermanovic |
| 111 | + |
| 112 | +**nzakas:** Sounds good. |
| 113 | + |
| 114 | +**fasttime:** Okay, I'll do that. |
| 115 | + |
| 116 | +**nzakas:** All right, I think that's it for today. Thanks everyone! |
| 117 | + |
| 118 | +**mdjermanovic:** Thanks! 👋 |
| 119 | + |
| 120 | +**nzakas:** (thanks @sam3k_ for the notes) |
| 121 | + |
| 122 | +**fasttime:** Thanks! Bye 👋 |
0 commit comments