tag:help.appveyor.com,2012-11-13:/discussions/suggestions/860-fyi-nodejs-500-is-outAppVeyor: Discussion 2018-10-19T08:17:33Ztag:help.appveyor.com,2012-11-13:Comment/383321482015-11-03T23:42:06Z2015-11-03T23:42:07ZFYI: Node.js 5.0.0 is out<div><p>+1 we depend on this for release native node binaries which
currently cannot support Node 5 on Windows.</p></div>xzyfertag:help.appveyor.com,2012-11-13:Comment/383321482015-11-04T00:25:38Z2015-11-04T00:25:38ZFYI: Node.js 5.0.0 is out<div><p>But it's already available on all build workers. Use this cmdlet
to switch:</p>
<pre>
<code>Install-Product node ''</code>
</pre></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/383321482015-11-04T01:12:59Z2015-11-04T01:13:00ZFYI: Node.js 5.0.0 is out<div><p>I don't believe this is applicable because we test under
multiple versions of Node.<br>
We're using the documented method for doing so - <a href="http://www.appveyor.com/docs/lang/nodejs-iojs#testing-under-multiple-versions-of-node-js-or-io-js">
http://www.appveyor.com/docs/lang/nodejs-iojs#testing-under-multipl...</a></p>
<p>However <code>nodejs_version: "5"</code> does not use Node
5.</p>
<p><a href="https://github.com/sass/node-sass/blob/master/appveyor.yml#L22-L30">
https://github.com/sass/node-sass/blob/master/appveyor.yml#L22-L30</a></p></div>xzyfertag:help.appveyor.com,2012-11-13:Comment/383321482015-11-04T01:14:52Z2015-11-04T01:14:52ZFYI: Node.js 5.0.0 is out<div><p>Can you drop a link to a build please?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/383321482015-11-04T01:20:14Z2015-11-04T01:20:14ZFYI: Node.js 5.0.0 is out<div><p>This is the latest build - <a href="https://ci.appveyor.com/project/sass/node-sass/build/1410">https://ci.appveyor.com/project/sass/node-sass/build/1410</a></p>
<p>(ignore the failure)</p></div>xzyfertag:help.appveyor.com,2012-11-13:Comment/383321482015-11-04T01:21:55Z2015-11-04T01:21:55ZFYI: Node.js 5.0.0 is out<div><p>That build uses this configuration: <a href="https://github.com/sass/node-sass/blob/8e1c12224c7a35aca6de4b85e740ae36bf3675dc/appveyor.yml#L57-L88">
https://github.com/sass/node-sass/blob/8e1c12224c7a35aca6de4b85e740...</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/383321482015-11-04T01:44:21Z2015-11-04T01:44:22ZFYI: Node.js 5.0.0 is out<div><p>Interesting. How is that possible given that commit is the head
of master and the appveyor config change happened days
beforehand?</p></div>Michael Mifsudtag:help.appveyor.com,2012-11-13:Comment/383321482015-11-04T01:50:00Z2015-11-04T01:50:00ZFYI: Node.js 5.0.0 is out<div><p>I think he says the second part of the config doesn't contain
Node 5 and<br>
that this part was used, not the "release" part above. The commit
is not<br>
relevant to this remark.</p></div>m.golebtag:help.appveyor.com,2012-11-13:Comment/383321482015-11-04T01:56:04Z2015-11-04T01:56:04ZFYI: Node.js 5.0.0 is out<div><p>I see. I misread the PR and assumed we were using Node 5 for
both. This should be patched on our end. I can confirm release does
build Node 5. Thank you both</p>
<p><a href="https://ci.appveyor.com/project/sass/node-sass/build/1411">https://ci.appveyor.com/project/sass/node-sass/build/1411</a></p></div>xzyfer