Skip to content

Conversation

@marco-ippolito
Copy link
Member

No description provided.

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/config
  • @nodejs/security-wg

@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. config Issues or PRs related to the config subsystem needs-ci PRs that need a full CI run. labels Nov 16, 2025
@codecov
Copy link

codecov bot commented Nov 16, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.53%. Comparing base (2271d2d) to head (1b5f598).
⚠️ Report is 28 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #60746   +/-   ##
=======================================
  Coverage   88.53%   88.53%           
=======================================
  Files         703      703           
  Lines      208226   208252   +26     
  Branches    40145    40146    +1     
=======================================
+ Hits       184352   184379   +27     
- Misses      15884    15891    +7     
+ Partials     7990     7982    -8     
Files with missing lines Coverage Δ
src/node_options.cc 77.75% <ø> (-0.11%) ⬇️
src/node_options.h 97.86% <ø> (ø)

... and 34 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ 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.

Copy link
Member

@RafaelGSS RafaelGSS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a suggestion, but I'm good landing it as it is and doing my suggestion in a follow up PR.

About the tests that were added, I don't think they really cover the permission guarantees, but I can improve that in a follow up PR. No problem.

Run with the configuration file:

```console
$ node --permission --experimental-default-config-file app.js
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't we enable --permission by default if the "permission" object exists in the config-file? So users won't need to pass --permission.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If that's the behaviour of the already present flags it should work out of the box! 🚀

Copy link
Member Author

@marco-ippolito marco-ippolito Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah its would be an improvement we can do it in a followup, that also might require us to review the flags we support. For example --test is not supported in the config file but --watch is (I think its just a discrepancy). We have to standardize the behavior

@marco-ippolito marco-ippolito added the request-ci Add this label to start a Jenkins CI on a PR. label Nov 17, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Nov 17, 2025
@nodejs-github-bot
Copy link
Collaborator

@marco-ippolito marco-ippolito added the commit-queue Add this label to land a pull request using GitHub Actions. label Nov 18, 2025
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Nov 18, 2025
@nodejs-github-bot nodejs-github-bot merged commit 0b6ae6d into nodejs:main Nov 18, 2025
79 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 0b6ae6d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c++ Issues and PRs that require attention from people who are familiar with C++. config Issues or PRs related to the config subsystem needs-ci PRs that need a full CI run.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants