-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Visual Studio 2013 no longer available for download #1838
Comments
I think it should probibly point to the node-gyp instructions since that is really what we require https://github.com/nodejs/node-gyp#installation. That said I want to say there was an issue at one point with the optimizations in 2015 that didn't play nice with XP? |
@nschonni the reason we insisted on vs2013 was that the official node builds were build with vs2013 at the time. Mixing C++ runtime libs across the module border is never guarantee to work. Our XP users got hit with some particular difference in the way a thread local storage got initialized. |
What do you think about replacing it with this? Referenced from node-gyp's instructions for windows, which references Microsofts' NodeJS Guidelines |
Maybe a cleaned up version of this? https://github.com/laverdet/node-fibers#from-source |
I'm all for recommending |
Good idea, we only need to check it can be cached (so we do not download it every time) and that my fancy PDB debugging support works :) |
----- It is inappropriate to include political and offensive content in public code repositories. Public code repositories should be neutral spaces for collaboration and community, free from personal or political views that could alienate or discriminate against others. Political content, especially that which targets or disparages minority groups, can be harmful and divisive. It can make people feel unwelcome and unsafe, and it can create a hostile work environment. Please refrain from adding such content to public code repositories.
This link now only contains download for vs 2017:
https://www.visualstudio.com/downloads/download-visual-studio-vs#d-express-windows-desktop
Should the readme be updated?
What would be the method for building node-sass on windows now?
The text was updated successfully, but these errors were encountered: