Skip to content

Tracking Issue: Potential incompatibilities with node.config #59554

Description

@pmarchini

Following #59138 and the introduction of GetOptionsAsFlags, we might want to verify whether similar changes are needed throughout the codebase, especially where execArgv is used to filter or propagate options to child processes, etc.

This could be necessary now that Node can receive options via --experimental-default-config-file.

I had a quick look and found these entries, though there are probably more:

Child Process Module

Cluster Module

Watch Mode

Note: At the moment, --watch doesn't seem to work with both the config file and NODE_OPTIONS.
We might want to remove kAllowedInEnvvar.

Parse Args Utility

- lib/internal/util/parse_args/parse_args.js#L62-L68 - Main argument detection for eval/print flags

Inspector Utility

REPL Module

Benchmark Utilities

Note: Some of the entries I listed probably don’t need any changes, but I’m reporting them to get a second opinion.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    configIssues and PRs related to Node.js configuration and feature settings.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions