您的位置:首页 > Web前端 > Node.js

Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 7.x

2018-02-05 23:31 736 查看
npm run dev 启动时,报了一大堆错误

Module build failed: Error: Missing binding E:\2017VocaSchool\vocationWeb\node_modules\node-sass\vendor\win32-x64-51\binding.node

Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 7.x

Found bindings for the following environments:

  - Windows 64-bit with Node.js 8.x

This usually happens because your environment has changed since running `npm install`.

Run `npm rebuild node-sass --force` to build the binding for your current environment.

    at module.exports (E:\2017VocaSchool\vocationWeb\node_modules\node-sass\lib\binding.js:15:13)

    at Object.<anonymous> (E:\2017VocaSchool\vocationWeb\node_modules\node-sass\lib\index.js:14:35)

    at Module._compile (module.js:571:32)

    at Object.Module._extensions..js (module.js:580:10)

    at Module.load (module.js:488:32)

    at tryModuleLoad (module.js:447:12)

    at Function.Module._load (module.js:439:3)

    at Module.require (module.js:498:17)

    at require (internal/module.js:20:19)

    at Object.<anonymous> (E:\2017VocaSchool\vocationWeb\node_modules\sass-loader\lib\loader.js:3:14)

    at Module._compile (module.js:571:32)

    at Object.Module._extensions..js (module.js:580:10)

    at Module.load (module.js:488:32)

    at tryModuleLoad (module.js:447:12)

    at Function.Module._load (module.js:439:3)

    at Module.require (module.js:498:17)

 @ ./~/vue-style-loader!./~/css-loader?{"minimize":false,"sourceMap":false}!./~/vue-loader/lib/style-compiler?{"id":"data-v-14fb6926","scoped":true,"hasInlineConfig":false}!./~/sass-loader/lib/loader.js?{"sourceMap":false}!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/views/flowDesign/startFlow.vue
4:14-396 13:3-17:5 14:22-404

 @ ./src/views/flowDesign/startFlow.vue

 @ ./src/routes.js

 @ ./src/main.js

 @ multi ./build/dev-client ./src/main.js

使用 npm rebuild node-sass,然后在更新一下npm update



然后在重新启动下,应该就好了。
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: 
相关文章推荐