Review requested:

• @nodejs/startup
• @nodejs/streams
• @nodejs/test_runner
• @nodejs/web-standards

it'd be great to get a PR that just fixes the value-named functions and disables the lint rule so that it can be released and maximally backported.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.32%. Comparing base (4ee7567) to head (c025626).
⚠️ Report is 594 commits behind head on main.

@@            Coverage Diff             @@
##             main   #57901      +/-   ##
==========================================
+ Coverage   90.05%   90.32%   +0.26%     
==========================================
  Files         714      730      +16     
  Lines      225876   234165    +8289     
  Branches    42737    43912    +1175     
==========================================
+ Hits       203408   211501    +8093     
- Misses      14244    14372     +128     
- Partials     8224     8292      +68     

... and 114 files with indirect coverage changes

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Hello, I've worked on the eslint rule for this one, i've just made some changes with the eslint's func-name-matching rule, and its ruletester.

You can check the work here: lib-name-functions

Let me know if you guys have any thoughts on this :>, and if all is good, i could send a PR to this PR's branch.

@LiviaMedeiros I've made the adjustments and here's the pull request to your branch, LiviaMedeiros#1

CI: https://ci.nodejs.org/job/node-test-pull-request/68346/

Hello, feel free to ping me if this needs to be merged, this might be blocked because of the Signed-off-by requirement

@louiellan apologies for late response and thank you!
To be honest, right now i'm not completely sure that this is the best way to move forward with these value() functions, as the issue is not really Node.js-specific. Should we consider submitting this rule to eslint itself so it's accessible by default? Of course in case if for some reason it gets rejected there, we can keep it as node-core/ option.

Now that you mentioned it, I realized that i only handled the explicit naming but not the concise notation functions (I'll work on it)

but we still need to have a separate node-core version here fixing also the same thing 'cause of primordials

as per submitting the rule to eslint, we'll need to make non-nodejs one (will work on it as well, I'll just mention you there and reference also the issue you made)

Commit linting is failing

CI: https://ci.nodejs.org/job/node-test-pull-request/73687/

CI: https://ci.nodejs.org/job/node-test-pull-request/73698/

- Validating Jenkins credentials
✔  Jenkins credentials valid
- Querying data for job/node-test-pull-request/73698/
[SyntaxError: Unexpected token '<', ..."    
  https://github.com/nodejs/node/actions/runs/29233234906

CI: https://ci.nodejs.org/job/node-test-pull-request/74771/

CI: https://ci.nodejs.org/job/node-test-pull-request/74777/

CI: https://ci.nodejs.org/job/node-test-pull-request/74782/

CI: https://ci.nodejs.org/job/node-test-pull-request/74789/

CI: https://ci.nodejs.org/job/node-test-pull-request/74796/

Landed in 727e2bc