node version 4.6.1
npm 2.15.9
stencil start
C:\Users\silk\AppData\Roaming\npm\node_modules\@bigcommerce\stencil-cli\node_modules\@bigcommerce\stencil-styles\node_modules\@bigcommerce\node-sass\lib\extensions.js:158
throw new Error([
^
Error: The `libsass` binding was not found in C:\Users\silk\AppData\Roaming\npm\node_modules\@bigcommerce\stencil-cli\node_modules\@bigcommerce\stencil-styles\node_modules\@bigcommerce\node-sass\vendor\win32-x64-46\binding.node
This usually happens because your node version has changed.
Run `npm rebuild node-sass` to build the binding for your current node version.
at Object.sass.getBinaryPath (C:\Users\silk\AppData\Roaming\npm\node_modules\@bigcommerce\stencil-cli\node_modules\@bigcommerce\stencil-styles\node_modules\@bigcommerce\node-sass\lib\extensions.js:158:11)
at Object.<anonymous> (C:\Users\silk\AppData\Roaming\npm\node_modules\@bigcommerce\stencil-cli\node_modules\@bigcommerce\stencil-styles\node_modules\@bigcommerce\node-sass\lib\index.js:16:36)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (C:\Users\silk\AppData\Roaming\npm\node_modules\@bigcommerce\stencil-cli\node_modules\@bigcommerce\stencil-styles\lib\styles.js:7:14)
at Module._compile (module.js:409:26)
Because the 'win32-x64-46_binding.node' file cannot be downloaded and the installation will report an error
So I made a local configuration after downloading it in the browser
SASS_BINARY_PATH=C:\Users\silk\AppData\Roaming\npm-cache\win32-x64-46_binding.node
In this way, the installation can be normal, but the above problems will occur. . . . .
Try changing the npm registry to Taobao’s mirror.
npm config set registry " https://registry.npm.taobao.org "
~/.npmrc
Due to project progress issues, I have gone to a colleague to copy the installed package. Once you find it, you can run it. This is a pitfall. It should be that the download of the .node file is unsuccessful and the local download cannot be compiled (although it can be installed successfully). .