:package: Install C++ Build Tools for Windows using npm
A new major release! I hope that windows-build-tools
is more useful than ever, with better error handling, more thoughtful logging, and optimization for the default case: Getting a Windows machine ready for compiling some C++.
PATH
. If Python is already installed, we do still leave it alone.windows-build-tools
now requires Node v8. Use [email protected]
if you're running Node v6.$env:PATH
handling on Windows. windows-build-tools
has a workaround included.• We will now force-exit the installation when the installation has finished. This is a workaround – there might be a bug with the Visual Studio installer (which signaled that it's done installing, but hasn't exited itself). Please continue to report any trouble ? ❤️
• Updated in-gfw
to 1.2.0.
windows-build-tools
v3.0 has been rewritten in TypeScript, making the module more resilient and bug-free. While I fully expect that end users will not have to change anything if they're currently using v2, the changes in behavior were big enough to warrant a new major version.
in-gfw
was upgraded, fixing commong ELIFECYCLE
issues for users within the Great Chinese Firewall.--dry-run-only
parameter was added, allowing users to see what the script would have done without actually installing anything.DEBUG="windows-build-tools"
is present, windows-build-tools
will now give more detailed information about parameters passed to the installers.ES2015
.npmignore
to only included required filesdist
dummy from GitHubThis release includes a few small changes that should make using this module easier.
This is a fairly big release and was properly tested in beta
, which is why we made a jump from 1.4
straight to 2.2
. The new major version has only one breaking change: The output changed from a spinner to actual details from the installers, allowing you to have a better understanding of what's happening underneath the hood.
--vs2017
)This version makes debugging PowerShell issues a whole lot easier, thanks to @jacobq.