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
module.js:682
return process.dlopen(module, path._makeLong(filename));
^
Error: The module '/home/calebjay/Documents/work/internal-admin/node_modules/bcrypt/lib/binding/bcrypt_lib.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
I have attempted
rm -rf node_modules followed by npm install
nvm use with various versions (the package.json lists "node": "10.13.0",)
npm rebuild
The error does not occur when the app is built and served outside of the vscode debugger - the error is unique to the debugger.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered:
@komali2
What is your default node.js version?
run node --version outside of VS Code and inside VS Code's integrated terminal.
Do you see the same version in both cases?
If you are using "nvm" or "nvs" you can add a "runtimeVersion": "x.y.z" to your launch config to make VS Code use a specific version of node.js.
npm version inside the integrated VSCode terminal is 10.13.0, and inside my actual terminal was 8.1... something. So, outside vscode I did
nvm use 10.13.0
npm rebuild
Then, I tried inside vscode to use the debugger, however, I'm still getting the following error:
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
This probably isn't a VSCODE bug, now that I see there's a difference in the terminal versions. Thank you anyway for your help. I'm a bit confused... I've no idea what versions of node to map against NODE_MODULE_VERSION 64 or 57, I've never seen them referred to that way...
CPUs
| Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 816)
-- | --
GPU Status
| 2d_canvas: unavailable_softwarechecker_imaging: disabled_offflash_3d: unavailable_softwareflash_stage3d: unavailable_softwareflash_stage3d_baseline: unavailable_softwaregpu_compositing: unavailable_softwaremultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarewebgl: enabled_readbackwebgl2: unavailable_off
Load (avg) | 1, 1, 1
Memory (System) | 15.42GB (4.06GB free)
Process Argv | --disable-gpu
Screen Reader | no
VM | 0%
Version: 1.29.1
Commit: bc24f98
Date: 2018-11-15T19:07:43.495Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
Steps to Reproduce:
I have attempted
rm -rf node_modules
followed bynpm install
nvm use
with various versions (the package.json lists"node": "10.13.0",
)npm rebuild
The error does not occur when the app is built and served outside of the vscode debugger - the error is unique to the debugger.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: