René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Specific code for \"The flag X must be used with extreme caution\"","articleBody":"### What is the problem this feature will solve?\n\nWhen using (for example) `--allow-child-process`, NodeJS (correctly) warns that this can allow bypassing the `--permission` protection:\n\n> (node:16778) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model.\n> (Use `node --trace-warnings ...` to show where the warning was created)\n\nThis warning is good, but if the developer is still confident in their setup, it would be useful to be able to suppress it without suppressing other warnings. Currently the only way to suppress this warning is with `--disable-warning=SecurityWarning`, which is far too broad.\n\n### What is the feature you are proposing to solve the problem?\n\n`--disable-warning` already accepts `code`s as well as types, but this particular warning has no `code` set: https://github.com/nodejs/node/blob/96a749b7b3b9dfe982d8d0056122d0d601af6cf7/lib/internal/process/pre_execution.js#L588-L590\n\nI'm suggesting picking a suitable code for this warning and adding it as the third argument to that call, perhaps something like `PERM0001` (though I don't know the naming convention for these codes).\n\n### What alternatives have you considered?\n\n_No response_","author":{"url":"https://github.com/davidje13","@type":"Person","name":"davidje13"},"datePublished":"2025-09-09T08:19:49Z","url":"https://github.com/nodejs/node/issues/59818"}