doc: add minutes for meeting 17 July 2024

[mhdawson]

No description provided.

[mhdawson]

@nschonni, @Trott I see you two had the most involvement in setting up the linting. It's been driving me a bit crazy that it complains about whitespace but does not identify what line is the problem. Is that the way it should be working?

[nschonni]

it seems like the https://github.com/nodejs/TSC/blob/main/.github/workflows/remark-lint-problem-matcher.json isn't commenting on the particular line, because the output isn't including the line details anymore. I'll see if I can figure out what broke.

[nschonni]

OK, did some digging, and it looks like that rule is actually a custom one from @Trott https://github.com/Trott/remark-lint-no-trailing-spaces. Maybe it needs an update for an api change in remark.

EX: I updated the remark-preset-lint-node to the latest, and it flagged a few new things (and correctly indicated the line/column of the issue). I had manually edited the ONBOARDING.md to have a trailing space outside an IDE, since EditorConfig autofixes it in VSCode

$ npm test

> tsc@1.0.0 test
> remark -qf .

meetings\io.js\2015-04-08.md
16:52-16:72 warning Unexpected reference to undefined definition, expected corresponding definition (`comment by @mikeal`) for a link or escaped opening bracket (`\[`) for regular text                       no-undefined-references remark-lint
17:50-17:92 warning Unexpected reference to undefined definition, expected corresponding definition (`comments by @silverwind and @fishrock123`) for a link or escaped opening bracket (`\[`) for regular text no-undefined-references remark-lint

ONBOARDING.md
            warning Remove trailing whitespace                                                                   
                                                                                              no-trailing-spaces      remark-lint

⚠ 3 warnings

[mhdawson]

@nschonni thanks for looking at the linter.

[Trott]

@nschonni @mhdawson I think when nodejs/remark-preset-lint-node#574 lands, that will generate a new release of the lint preset that will fix the issue with reporting lines and columns for trailing spaces. Unfortunately, that's currently blocked by the wonkiness we're seeing with Node.js 22 that I'm sure everyone is aware of and eager to see fixed.

[Trott]

OK, @mhdawson! If you rebase against origin/main and run npm ci, you should be all set. The trailing spaces linter will now tell you where to look.

[mhdawson]

@nodejs/tsc could be good to get some approvals so I can land.

@Trott since the linter is green on this one, I'll look forward to the info for future PRs. Thanks for your help in getting it fixed.