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

Different results in npm audit #17475

New Issue
Closed
opened 2026-01-31 05:43:33 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 05:43:33 +00:00
Owner
Copy Link

Originally created by @nirgranth on GitHub (May 13, 2022).

Windows Terminal version

1.12.19083.0

Windows build number

10.0.22000.318

Other Software

No response

Steps to reproduce

recently upgraded for win 10 to 11
running npm audit in cmd, cant even fix it with npm audit fix,

idk if this is the right place for this i cant seem to find the cmd/cli repo

Expected Behavior

Everyting matches

Actual Behavior

Uploading image.png…

Originally created by @nirgranth on GitHub (May 13, 2022). ### Windows Terminal version 1.12.19083.0 ### Windows build number 10.0.22000.318 ### Other Software _No response_ ### Steps to reproduce recently upgraded for win 10 to 11 running npm audit in cmd, cant even fix it with npm audit fix, idk if this is the right place for this i cant seem to find the cmd/cli repo ### Expected Behavior Everyting matches ### Actual Behavior ![Uploading image.png…]()
claunia commented 2026-01-31 05:43:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 13, 2022):

I'm sorry, it looks like the image you uploaded didn't work out. Can you re-send it?

@DHowett commented on GitHub (May 13, 2022): I'm sorry, it looks like the image you uploaded didn't work out. Can you re-send it?
claunia commented 2026-01-31 05:43:35 +00:00
Author
Owner
Copy Link

@nirgranth commented on GitHub (May 13, 2022):

image

@nirgranth commented on GitHub (May 13, 2022): ![image](https://user-images.githubusercontent.com/48947296/168225747-8ceb404f-441e-49c1-9fbe-1f499d765113.png)
claunia commented 2026-01-31 05:43:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 13, 2022):

If you run where npm in each, do you get the same NPM/? I suspect this might have to do with the two windows having different PATHs.

@zadjii-msft commented on GitHub (May 13, 2022): If you run `where npm` in each, do you get the same NPM/? I suspect this might have to do with the two windows having different `PATH`s.
claunia commented 2026-01-31 05:43:35 +00:00
Author
Owner
Copy Link

@nirgranth commented on GitHub (May 14, 2022):

image

npm help-
image

@nirgranth commented on GitHub (May 14, 2022): ![image](https://user-images.githubusercontent.com/48947296/168405285-b15c8dda-6fa6-45a8-a7db-1a2bba6bc7de.png) npm help- ![image](https://user-images.githubusercontent.com/48947296/168405311-a35e9578-6169-45fb-ab68-37d30b99ae66.png)
claunia commented 2026-01-31 05:43:36 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (May 14, 2022):

@Nirgranth when using admin, find where your packages are located with npm root and npm root -g. Also, check if C:\Windows\System32\node_modules is present. Looks like you have vulnerable node packages installed in C:\Windows\System32\node_modules.

@elsaco commented on GitHub (May 14, 2022): @Nirgranth when using admin, find where your packages are located with `npm root` and `npm root -g`. Also, check if `C:\Windows\System32\node_modules` is present. Looks like you have vulnerable node packages installed in `C:\Windows\System32\node_modules`.
claunia commented 2026-01-31 05:43:36 +00:00
Author
Owner
Copy Link

@nirgranth commented on GitHub (May 14, 2022):

@Nirgranth when using admin, find where your packages are located with npm root and npm root -g. Also, check if C:\Windows\System32\node_modules is present. Looks like you have vulnerable node packages installed in C:\Windows\System32\node_modules.

yup you are correct, how do i fix it

@nirgranth commented on GitHub (May 14, 2022): > @Nirgranth when using admin, find where your packages are located with `npm root` and `npm root -g`. Also, check if `C:\Windows\System32\node_modules` is present. Looks like you have vulnerable node packages installed in `C:\Windows\System32\node_modules`. yup you are correct, how do i fix it
claunia commented 2026-01-31 05:43:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 16, 2022):

find where your packages are located with npm root and npm root -g. Also, check if C:\Windows\System32\node_modules is present. Looks like you have vulnerable node packages installed in C:\Windows\System32\node_modules.

yup you are correct, how do i fix it

Honestly I don't know - you might be able to find more help on StackOverflow or the npm repo itself. Since this doesn't seem like a Terminal-specific issue, I'm gonna close this out. Thanks!

@zadjii-msft commented on GitHub (May 16, 2022): > > find where your packages are located with `npm root` and `npm root -g`. Also, check if `C:\Windows\System32\node_modules` is present. Looks like you have vulnerable node packages installed in `C:\Windows\System32\node_modules`. > > yup you are correct, how do i fix it Honestly I don't know - you might be able to find more help on StackOverflow or the npm repo itself. Since this doesn't seem like a Terminal-specific issue, I'm gonna close this out. Thanks!
claunia commented 2026-01-31 05:43:37 +00:00
Author
Owner
Copy Link

@nirgranth commented on GitHub (May 16, 2022):

Honestly I don't know - you might be able to find more help on StackOverflow or the npm repo itself. Since this doesn't seem like a Terminal-specific issue, I'm gonna close this out. Thanks!
okay thanks

@nirgranth commented on GitHub (May 16, 2022): > Honestly I don't know - you might be able to find more help on StackOverflow or the npm repo itself. Since this doesn't seem like a Terminal-specific issue, I'm gonna close this out. Thanks! okay thanks
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 Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-External
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#17475
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?