doc: add link to VSCode config in testing

[trivikr]

Refs: https://github.com/orgs/nodejs/teams/collaborators/discussions/58

This config will help contributors to run/debug tests on VSCode

Checklist

• documentation is changed or added
• commit message follows commit guidelines

[nodejs-github-bot]

@trivikr build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1447/pipeline

[Trott]

That config repo was transferred into the org without opening an issue in the admin repo to discuss. (That process is not easy to surface if you don't know where it is, so I understand why it was missed!)

The config repo lacks things that might have been insisted upon during that process. For example, there is no Code of Conduct and no LICENSE file. 😱 I don't know if transferring it out is the answer and then opening the issue in the admin repo? @nodejs/tsc @nodejs/community-committee

I'm not sure we want to add IDE-specific configurations into BUILDING.md. (I'm also not sure we don't. Curious what others think.)

Not actually going to block this...

[trivikr]

Updates about node-vscode-config:

• Issue for transfer of ownership was created at Transferring ownership of node-vscode-config admin#260
• PR to add Code Of Conduct is created at doc: add Code of Conduct node-code-ide-configs#2
• PR to add MIT License is created at doc: add MIT License node-code-ide-configs#3

[jasnell]

While I love VSCode and use it daily, I'd much prefer moving this kind of stuff into a separate guide that can detail the use of multiple tools.

[refack]

I'd much prefer moving this kind of stuff into a separate guide that can detail the use of multiple tools.

👍

I'm not sure we want to add IDE-specific configurations into BUILDING.md.

Personally I'd like to see the guide shrink... I feel that as the top level guide it's too verbose. So I'm -1 on adding more specific cases to it, including IDE specific instructions, unless that can help to un-verbose the guide.

That said, IMHO this would be useful to have in a separate guide, referred to from the main guide.

[trivikr]

@jasnell Steps taken:

• Updated the names suggested for the repo in Rename the repo to make it editor agnostic? node-code-ide-configs#1
• Updated this PR with the latest popular name (i.e. node-code-ide-configs)
• Created PR to move VSCode specific configs to .vscode folder doc: Move VSCode configs to .vscode folder node-code-ide-configs#4

[trivikr]

Since I ran out of time, I forgot to show the VSCode launch configs being used in my NodeConfEU talk today.

Can we push this code so that new contributors don't get stuck finding out the VSCode launch config while contributing to Node?
On Google, searching for node VSCode Config shows which VSCode Config to use while debugging Node.js, and not Node.js core.

[Trott]

At the risk of getting too picky here, should we refrain from having developer stuff in the build doc and instead put that in CONTRIBUTING.md or something else that is aimed at developers working on Node.js core? BUILDING.md has a broader audience than that IMO.

[Trott]

(Granted, there are probably things in BUILDING.md already that, based on that criteria, should be moved out, like coverage generation.)

[trivikr]

Added tsc-agenda label, for discussions related to following questions:

• What should be the name for new repo which stores editor configs?
  • Issue created at Rename the repo to make it editor agnostic? node-code-ide-configs#1, suggestions as of 11/09 are node-editor-configs and node-code-ide-configs
• Where should we link the repo from Node.js core? Should it link from BUILDING.md or CONTRIBUTING.md or somewhere else?

Follow up required on PRs:

• Adding Code of Conduct doc: add Code of Conduct node-code-ide-configs#2
• Adding MIT License doc: add MIT License node-code-ide-configs#3
• Move VSCode configs to .vscode folder doc: Move VSCode configs to .vscode folder node-code-ide-configs#4

[trivikr]

Removed tsc-agenda label as we agreed on name node-code-ide-configs in nodejs/TSC#633

[trivikr]

@Trott @jasnell This PR is ready for review.

[trivikr]

Landed in e55d653