Closed hartman closed 7 years ago
I think the issue is that we're still using an old version of node-sass which doesn't have macos sierra binaries. There are some reasons we can't update to a newever version of node-sass (we're relying on a feature that was removed because it didn't conform to ruby sass). Unfortunately, there isn't a good fix for this.
@gkatsev I think that would be sass/node-sass#1484
Any possible to backport this fix to node-sass 3.3? node-sass 3.4 introduces breaking changes
unfortunately it is not possible to back port this change because it's in the native code that talks to LibSass.
Oh, it's a problem with node 6?
Description
grunt throws me stack traces. Suspect related to browserify. Verified on clean install of modules, after rm -rf and npm cache clean.
Steps to reproduce
Explain in detail the exact steps necessary to reproduce the issue.
Results
Expected
No errors
Error output
npm ls output:
Additional Information
versions
grunt-cli: v1.2.0 grunt: v0.4.5 npm: 3.10.8 node: v6.8.0
videojs
master (5.12.3)
OSes
MacOS Sierra