René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"'socket npm' overrides NODE_OPTIONS","articleBody":"To demo, in package.json:\n\n```js\n  \"scripts\": {\n    \"echo\": \"echo $NODE_OPTIONS\",\n  }\n```\n\nRunning npm directly:\n\n```\n➜ NODE_OPTIONS=test npm run echo\n\n\u003e echo\n\u003e echo $NODE_OPTIONS\n\ntest\n```\n\nRunning with socket-cli:\n\n```\n➜ NODE_OPTIONS=test socket npm run echo\n   _____         _       _        /---------------\n  |   __|___ ___| |_ ___| |_      | CLI: v1.1.34\n  |__   | . |  _| '_| -_|  _|     | token: (not set), org: (not set)\n  |_____|___|___|_,_|___|_|.dev   | Command: `socket npm`, cwd: ~/.../\n\n\n\u003e echo\n\u003e echo $NODE_OPTIONS\n\n'--permission --allow-child-process --allow-fs-read=* --allow-fs-write=/home/.../* --allow-fs-write=/home/.../npm-installation/* --allow-fs-write=/home/.../.npm/*'\n```\n\nThis makes it impossible to use `socket npm` as a drop in replacement if you configure NODE_OPTIONS globally, since any such kind of configuration is ignored.\n\nImo Socket should include globally set options in addition to it's own additions - it shouldn't replace them entirely.","author":{"url":"https://github.com/pimterry","@type":"Person","name":"pimterry"},"datePublished":"2026-01-12T10:13:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1036/socket-cli/issues/1036"}