-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
from Nodejs 13 breaks on Windows 7 - procedure entry point GetHostNameW could not be located (as libuv) #41297
Comments
Windows 7 is no longer supported. You will have to upgrade or change your OS to use the latest versions of node. |
This comment was marked as abuse.
This comment was marked as abuse.
@introspection3 The open source license grants you the freedom to use Node.js (and libuv). It does not guarantee commitments of other people's time. Maintaining Windows parity is difficult enough for the volunteers who make this software available. Adding the complication of trying to support EOL operating systems is not something we're likely to do. Sorry. You can use Node.js 12.x, though. It is supported until April 2022. |
please make available nodejs to windows 7!! |
The open source license grants you the freedom to use Node.js. It does not guarantee commitments of other people's time. Please be respectful and manage your expectations. I've locked this issue. |
Version
Platform
windows 7
Subsystem
all
What steps will reproduce the bug?
from Nodejs 13 breaks on Windows 7 - procedure entry point GetHostNameW could not be located
as libuv,so please tell libuv as you have more power(libuv ignore us)
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
d
The text was updated successfully, but these errors were encountered: