starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

When I install node, I can't use it in new tab of opend terminal task. #18840

New Issue
Open
opened 2026-01-31 06:25:59 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:25:59 +00:00
Owner
Copy Link

Originally created by @char-46 on GitHub (Nov 6, 2022).

Windows Terminal version

1.16.2642.0

Windows build number

10.0.22621.755

Other Software

No response

Steps to reproduce

  • Open Winodws Terminal
  • Setup node
  • Open new tab on Windows Terminal
  • Type npm

Expected Behavior

When I install node on my PC, It changes PATH environment variable. I expceted it can update its environment automatically. So I open a new tab on a exist window. I expced it can use npm right away.

Actual Behavior

When I typed npm, the powershell tell me that:
npm: The term 'ver' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
I tried use Run command to open a new powershell task to update its environment, but it follows my config then merged to the Windows Terminal window which exists and doesn't update its environment(i.e. the old process wt.exe's environment). So that I still can't use the npm command on the new powershell tab.

why I have to kill all process which running on the old wt process then that I can just use the new environment. if I don't accept that I'll have to make my dessktop mess?

Originally created by @char-46 on GitHub (Nov 6, 2022). ### Windows Terminal version 1.16.2642.0 ### Windows build number 10.0.22621.755 ### Other Software _No response_ ### Steps to reproduce * Open Winodws Terminal * Setup node * Open new tab on Windows Terminal * Type npm ### Expected Behavior When I install node on my PC, It changes PATH environment variable. I expceted it can update its environment automatically. So I open a new tab on a exist window. I expced it can use `npm` right away. ### Actual Behavior When I typed `npm`, the powershell tell me that: `npm: The term 'ver' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.` I tried use Run command to open a new powershell task to update its environment, but it follows my config then merged to the Windows Terminal window which exists and doesn't update its environment(i.e. the old process wt.exe's environment). So that I still can't use the `npm` command on the new powershell tab. why I have to kill all process which running on the old wt process then that I can just use the new environment. if I don't accept that I'll have to make my dessktop mess?
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:25:59 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18840
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?