1.4.1

This release fixes an issue with the Python installer not correctly being found.

1.3.1

Another tiny patch release: No fixes, but a few dependency bumps. Also, windows-build-tools now installs Python 2.7.13 (previously, int installed 2.7.11).

1.2.1

A tiny patch release that fixes an error during Python installation if the username contains spaces.

1.2.0

This release updates a few dependencies and adds the ability to add the Python installation to the user's $PATH. Previously, windows-build-tools would install Python for npm only.

npm [--add-python-to-path] [...all other arguments] install --global windows-build-tools

--add-python-to-path: Add Python to the environment, allowing you to type python.exe in any shell. Defaults to false.

1.1.0

This release is tiny, it simply fixes some internal tests and adds a new silent option:

• --silent: The script will not output any information.

1.0.0: New features! More security!

🎉 Our version 1.0 comes with a few new fancy features - mostly the ability to customize how exactly the build tools are installed. If you check out the Readme, you'll find a few command line arguments allowing you to specify proxies, the number of sockets used for the download, or even an admin configuration file for the VCC build tools - and those are just three examples out of a list of around 30.

Special thanks to Liang Gong (@JacksonGL) and Danny Grander (@grnd) for a security report (we were using http instead of https, shame on us) - and 刘祺 (@gucong3000), who made sure that the tools install speedy in all places of the world.