why WSL is not good idea for development

Honestly i tried to use WSL (Windows Subsystem for Linux) many times and gave up because of time or other constraints, finally now i decided to use because in my windows pc, i am using old nodejs and a project required latest nodejs

everything went fine but then, i want to do a quick npm run xxx on windows terminal and it throws error because….

Error: Missing binding C:\laragon\www\v2-gsk\node_modules\node-sass\vendor\win32-x64-57\binding.node
Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 8.x

Found bindings for the following environments:

  • Linux 64-bit with Node.js 12.x

This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass to download the binding for your current environment.

at module.exports (C:\laragon\www\v2-gsk\node_modules\node-sass\lib\binding.js:15:13)
at Object. (C:\laragon\www\v2-gsk\node_modules\node-sass\lib\index.js:14:35)
at Module._compile (module.js:652:30)
at Module._compile (C:\laragon\www\v2-gsk\node_modules\pirates\lib\index.js:99:24)
at Module._extensions..js (module.js:663:10)
at Object.newLoader as .js
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
error Command failed with exit code 1.

so… as error says..if you use WSL you should stick to it all the time, but in reality i switch to babun cmder (and rarely git cmd or cmd) depending upon situations but if you use WSL you will lose that freedom.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.