René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow setting `--max-heap-size` in `NODE_OPTIONS`","articleBody":"### What is the problem this feature will solve?\n\nV8 supports this flag for a while now (see [9306](https://issues.chromium.org/issues/42212488)), and it's even documented under `--v8-options` ([see](https://github.com/nodejs/node/blob/v24.2.0/deps/v8/src/flags/flag-definitions.h#L2062-L2066)). However, it's not yet supported to set it with `NODE_OPTIONS` environment variable as it is for some other similar flags like `--max-old-space-size` ([see](https://github.com/nodejs/node/blob/v24.2.0/src/node_options.cc#L1073)).\n\nFor instance, a process will fail with the following error if we try to do this:\n```\n♪ NODE_OPTIONS='--max-heap-size=750' node\nnode: --max-heap-size= is not allowed in NODE_OPTIONS\n```\n\n### What is the feature you are proposing to solve the problem?\n\nAllow setting `--max-heap-size` in the `NODE_OPTIONS` environment variable.\n\n### What alternatives have you considered?\n\nAt the moment, we are forced to set this flag directly in the command line, but this is a bit inconvenient when we have to manage several services and want to dynamically calculate the maximum heap size in containerized environments (e.g., based on the memory limit imposed for a pod in a Kubernetes cluster).","author":{"url":"https://github.com/hpedrorodrigues","@type":"Person","name":"hpedrorodrigues"},"datePublished":"2025-06-12T03:19:25.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/58686/node/issues/58686"}