-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Closed
Labels
apiIssues related to APIIssues related to APIbugSomething isn't workingSomething isn't workingstatus: fixed in next releaseThe issue will be closed once next release is availableThe issue will be closed once next release is available
Description
Raycast version: 1.25.1
Description
environment variables NODE_ENV and NODE_PATH are supposed to only be set for the node process running the command, however OpenAction copies them into the opened application window
this causes issues for example when using OpenAction to launch vscode, the integrated terminal inside vscode will get the two environment variables and thus behavior of node / npm changes unexpectedly
slack convo
https://raycastcommunity.slack.com/archives/C01A0R0NXGQ/p1635090222013200
Steps To Reproduce
- make sure vscode is not running
- run “Search Recent Projects” command and use the command to open a vscode window
- in integrated terminal inside the vscode window, check environment variables
The current behavior
two environment variables are set
➤ env | rg NODE_
NODE_ENV=production
NODE_PATH=/Applications/Raycast.app/Contents/Resources/RaycastCommands_RaycastCommands.bundle/Contents/Resources/api/node_modules
The expected behavior
the two environment variables should not be copied into the opened window
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
apiIssues related to APIIssues related to APIbugSomething isn't workingSomething isn't workingstatus: fixed in next releaseThe issue will be closed once next release is availableThe issue will be closed once next release is available