v5.2.0

Changelog

• Updated various dependencies to their latest versions. There should be no change in the behavior of windows-build-tools.

v5.1.0

Changelog

• Updated debug and string-width dependencies. There should be no change in the behavior of windows-build-tools.

v5.0.0

Changelog

• For VS2015, removes an outdated success string that made the npm installation exit long before Visual Studio was installed. Changed the installation success test to include testing with real log files.
• For VS2017, included a SDK in the installation and fixed the node-gyp configuration. Also, made it only possible to succeed or fail, previously the installer reported both (the strings to detect failure are very generic, but look good to me, it makes sense that success takes precedence and anything else is a failure).
• Makes VS2017 the default.

v4.0.0

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++.

Changelog

• ⚠️ Breaking change: Python is now always added to the PATH. If Python is already installed, we do still leave it alone.
• ⚠️ Breaking change: windows-build-tools now requires Node v8. Use windows-build-tools@3.1.0 if you're running Node v6.
• 🆕 Offline installers: Instead of downloading installers on each run, you can now supply a directory with already downloaded installers, which is useful on CI machines.
• 🆕 Some npm versions had a bug that lead to incorrect $env:PATH handling on Windows. windows-build-tools has a workaround included.
• 🆕 Logging has been cleaned up dramatically.
• 🐛 Python installation failures will be handled better.
• ⛏ Infrastructure: Update TypeScript (and related development dependencies)
• 📝 Updated the readme with helpful tips.

v3.1.0

Changelog

• 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.

v3.0.1

Changelog

• Update the readme (thanks, @mikemaccana)
• Add additional checks for whether or not installation is done (thanks, @sanderdegroot)
• Update dependencies
• Ran "npm audit fix"

v3.0.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.

Changelog

• in-gfw was upgraded, fixing commong ELIFECYCLE issues for users within the Great Chinese Firewall.
• Python is no longer being installed if a version of Python 2.x can be found on the system and is reachable in the current terminal session.
• A --dry-run-only parameter was added, allowing users to see what the script would have done without actually installing anything.
• When DEBUG="windows-build-tools" is present, windows-build-tools will now give more detailed information about parameters passed to the installers.
• Internal: Moved to TypeScript, compile strictly against ES2015
• Internal: Moved to Jest for unit testing
• Internal: Updated .npmignore to only included required files
• Internal: Removed dist dummy from GitHub

v2.3.0

This release includes a few small changes that should make using this module easier.

• Users in China will automatically be switched over to use a mirror of Python (thanks to @gucong3000)
• Downloads will now be executed in parallel (thanks to @gucong3000)
• VCC build tools errors now show more detailed output (thanks to @pronebird)

v2.2.1

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.

Changes

• Support for Visual Studio 2017 Build Tools (--vs2017)
• Output includes last recorded status from the installers
• Updated dependencies
• Fixed various bugs around old logfiles

1.4.2

This version makes debugging PowerShell issues a whole lot easier, thanks to @jacobq.