Skip to content
This repository has been archived by the owner on Sep 11, 2021. It is now read-only.

Set environment vars per package #13

Closed
massimocode opened this issue Jul 25, 2016 · 3 comments
Closed

Set environment vars per package #13

massimocode opened this issue Jul 25, 2016 · 3 comments

Comments

@massimocode
Copy link
Contributor

Hi

So following #12 I noticed (from the Task Manager) that the build tools were installing. I let these install and also installed python manually from the version that was downloaded by running this tool.

However, I still can't install node-sass@3.4.2. I get the following error:
MSBUILD : error MSB4132: The tools version "2.0" is unrecognized. Available tools versions are "14.0", "4.0".

Any ideas?

@massimocode
Copy link
Contributor Author

I have found the solution discussed here: chjj/pty.js#60

Basically I ran the following command:
npm config set msvs_version 2015 --global

I wanted to make a PR but I realised that there seems to be a script that does this once the downloads are complete. Considering the installation of Python was unsuccessful for me, that explains why this was not done automatically.

Feel free to close this issue if you think nothing further should be done... perhaps the environment variables for each thing should be done separately in case one fails and is installed manually by the user?

@felixrieseberg
Copy link
Owner

I agree, this makes a lot of sense.

@felixrieseberg felixrieseberg changed the title node-sass complains about missing build tools v2.0 Set environment vars per package Aug 11, 2016
@jacobq
Copy link
Collaborator

jacobq commented Dec 18, 2019

I'm closing this issue due to age / inactivity. If there is still interest and actionable steps then feel free to reopen.

@jacobq jacobq closed this as completed Dec 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants