You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The exeDependency for Windows always pulls in the 32-bit node.exe even when running a 64-bit version of windows.
I created PR #46 which will pull in the 64-bit version of node.exe when running 64-bit versions of Windows.
The specific nuisance this issue causes if you use node-sass, the node-sass installer looks at the process architecture to determine which libsass binding to install, and if I've already installed node-sass manually through an 'npm install' that will have installed the 64-bit binding in node_modules, and that will generate errors when gradle-node-plugin tries to run it with node.exe*32.
The text was updated successfully, but these errors were encountered:
The exeDependency for Windows always pulls in the 32-bit node.exe even when running a 64-bit version of windows.
I created PR #46 which will pull in the 64-bit version of node.exe when running 64-bit versions of Windows.
The specific nuisance this issue causes if you use node-sass, the node-sass installer looks at the process architecture to determine which libsass binding to install, and if I've already installed node-sass manually through an 'npm install' that will have installed the 64-bit binding in node_modules, and that will generate errors when gradle-node-plugin tries to run it with node.exe*32.
The text was updated successfully, but these errors were encountered: