[Terminal Finder] - Bug with environment variable NODE_ENV

[bastienlimbour]

Extension – Terminal Finder

Author: yedongze

Description

When i use the "Finder -> iTerm" command in Raycast it automatically initialize an environment variable NODE_ENV=production globally on my mac.
And it's not pleasant as a developer to have this behavior..

Steps To Reproduce

1. Open a folder in the finder
2. Open Raycast with shortcut
3. Use the command "Finder -> iTerm" in Raycast
4. The terminal opens fine but an environment variable NODE_ENV is set to "production" globally on my Mac

The current behavior

The terminal is opened with the NODE_ENV=production global environment variable

The expected behavior

Open the terminal without the NODE_ENV=production global environment variable

Raycast version

Raycast Version 1.41.1

macOS version

macOS Monterey version 12.6 - Macbook Pro 2021 - M1 Pro

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[stale]

I'm closing this due to inactivity; feel free to comment in the thread when you're ready to continue working on it 🙂
You can also catch us in Slack if you want to discuss.