Daniel Laufer

I set my nvm to v8.3.0 and this error went away. It could be that it just happened at the same time, but figured I'd throw that in here.

@akashziffy I think this might be a node version issue. I had this issue and then I set nvm to v8.3.0 and then ran `npm rebuild node-sass --force` and the...