Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility issue with new Windows 10 Terminal #38

Closed
absalomedia opened this issue Nov 11, 2019 · 3 comments
Closed

Compatibility issue with new Windows 10 Terminal #38

absalomedia opened this issue Nov 11, 2019 · 3 comments

Comments

@absalomedia
Copy link
Contributor

Node Vagrant needs to be compatible with the coming release of Windows 10 Terminal (release 2020).

Otherwise you lose platform compatibility, as seen in errror thrown here: absalomedia/vagrant-manager#21

@edin-m
Copy link
Owner

edin-m commented Nov 11, 2019

Can't figure out the root cause... If I understand correctly it's: a) node's spawn b) PowerShell exe name and/or version c) Windows .NET dependencies?

@absalomedia
Copy link
Contributor Author

Would it be further up the line than your work? Inside Vagrant itself? Considering it's the thing trying to detect Powershell version?

@edin-m
Copy link
Owner

edin-m commented Dec 4, 2019

Yeah, this is something upstream probably. This lib is calling nodejs child_process, and from I can see in the screenshots, it may be something to do with the nodejs child_process side.

@edin-m edin-m closed this as completed Apr 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants