title: Failed at the node-sass@4.7.2 postinstall script
body: <p>I just downloaded the latest version of <code>node.js</code> and I've been trying to do <code>npm install</code> on one of my projects but saying:</p>
  
  <blockquote>
    <p>Failed at the node-sass@4.7.2 postinstall script.</p>
  </blockquote>
  
  <p>I tried doing: <code>npm rebuild node-sass --force</code> which didn't do anything either. </p>
  
  <p><a href="https://i.stack.imgur.com/xYygY.png" rel="noreferrer"><img src="https://i.stack.imgur.com/xYygY.png" alt="enter image description here"></a></p>
  
  <p>The error log returns this: </p>
  
  <pre><code>3209 warn angularfire2@5.0.0-rc.10 requires a peer of @angular/common@^6.0.0 
  but none is installed. You must install peer dependencies yourself.
  3210 warn angularfire2@5.0.0-rc.10 requires a peer of @angular/core@^6.0.0 but none is installed. You must install peer dependencies yourself.
  3211 warn angularfire2@5.0.0-rc.10 requires a peer of @angular/platform-browser@^6.0.0 but none is installed. You must install peer dependencies yourself.
  3212 warn angularfire2@5.0.0-rc.10 requires a peer of @angular/platform-browser-dynamic@^6.0.0 but none is installed. You must install peer dependencies yourself.
  3213 warn angularfire2@5.0.0-rc.10 requires a peer of firebase@^5.0.3 but none is installed. You must install peer dependencies yourself.
  3214 warn angularfire2@5.0.0-rc.10 requires a peer of rxjs@^6.0.0 but none is installed. You must install peer dependencies yourself.
  3215 warn geofire@4.1.2 requires a peer of firebase@^2.4.0 || 3.x.x but none is installed. You must install peer dependencies yourself.
  3216 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\fsevents):
  3217 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
  3218 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS:    darwin
  3218 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch:  any
  3218 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS:   win32
  3218 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
  3219 verbose stack Error: node-sass@4.7.2 postinstall: `node scripts/build.js`
  3219 verbose stack Exit status 1
  3219 verbose stack     at EventEmitter.&lt;anonymous&gt; (C:\Users\Simon K\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:283:16)
  3219 verbose stack     at emitTwo (events.js:126:13)
  3219 verbose stack     at EventEmitter.emit (events.js:214:7)
  3219 verbose stack     at ChildProcess.&lt;anonymous&gt; (C:\Users\Simon K\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
  3219 verbose stack     at emitTwo (events.js:126:13)
  3219 verbose stack     at ChildProcess.emit (events.js:214:7)
  3219 verbose stack     at maybeClose (internal/child_process.js:925:16)
  3219 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
  3220 verbose pkgid node-sass@4.7.2
  3221 verbose cwd C:\xampp\htdocs\project x\projectx
  3222 verbose Windows_NT 10.0.16299
  3223 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Simon K\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
  3224 verbose node v8.11.2
  3225 verbose npm  v6.0.1
  3226 error code ELIFECYCLE
  3227 error errno 1
  3228 error node-sass@4.7.2 postinstall: `node scripts/build.js`
  3228 error Exit status 1
  3229 error Failed at the node-sass@4.7.2 postinstall script.
  3229 error This is probably not a problem with npm. There is likely additional logging output above.
  3230 verbose exit [ 1, true ]
  </code></pre>
  
  <p>and my npm and node versions are:</p>
  
  <pre><code>2 info using npm@6.0.1
  3 info using node@v8.11.2
  </code></pre>
  
  <p>I've also tried completely deleting my <code>node_modules</code> folder and running <code>npm install</code> again but that didn't work.</p>
  
  <p>One possible reason for this could be that <em>before</em> I updated node I followed this persons suggestion: <a href="https://github.com/angular/angular-cli/issues/10527" rel="noreferrer">https://github.com/angular/angular-cli/issues/10527</a></p>
  
  <p>Where he says:</p>
  
  <blockquote>
    <ol>
    <li>Download and save a local copy of the correct version of node-sass
    binary - win32-x64-64_binding.node. For example download it to the
    following location: C:\node-sass\win32-x64-64_binding.node </li>
    <li>Provide
    reference to the full path of the node-sass binary file in the
    sass_binary_path npm configuration parameter (in the ~/.npmrc file):
    npm config set sass_binary_path  For
    example, npm config set sass_binary_path
    C:\node-sass\win32-x64-64_binding.node </li>
    <li>Run the npm install command
    again to install @angular/cli correctly. </li>
    <li>Execute ng serve or npm start
    and your should be past the problem.</li>
    </ol>
  </blockquote>
  
  <p>I don't know if this is related.. I wouldn't think so since I've updated node, tried to force <code>node-sass</code> rebuild but I don't know.</p>
  
  <p>Any ideas/advice on how to fix this? Thank you!</p>