Error: Cannot find module '.../node_modules/@tensorflow/tfjs-node/lib/napi-v4/tfjs_binding.node'
See original GitHub issueTo get help from the community, we encourage using Stack Overflow and the tensorflow.js
tag.
TensorFlow.js version
“@tensorflow/tfjs-core@1.2.9”:
Browser version
Describe the problem or feature request
Error: Cannot find module ‘…/node_modules/@tensorflow/tfjs-node/lib/napi-v4/tfjs_binding.node’
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:34 (10 by maintainers)
Top Results From Across the Web
Error: cannot find module [Node npm Error Solved]
In this article, I'm going to show you how to fix the error. Why the "Error: cannot find module" Occurs. This error occurs...
Read more >How do I resolve "Cannot find module" error using Node.js?
Using npm install installs the module into the current directory only (in a subdirectory called node_modules ). Is app.js located under ...
Read more >How to Fix
Just installed node v5 and running npm in command line produces said error. OS X 10.10.5 How to Fix (For now) (Edited in...
Read more >Fix Global Installs Not Working | "Cannot find module" error FIX
Getting " Cannot find module " after installing something globally (with -g)? Well, this video shows you how to fix global package/module ...
Read more >How to resolve "Cannot find module" error in Node
When you are working in Node, you will sometimes encounter the error Cannot find module 'module-name' with the error code MODULE_NOT_FOUND .
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Workaround:
npm rebuild @tensorflow/tfjs-node --build-from-source
I was facing this issue on WSL 2 using Ubuntu 18.04 Fixed it with the following commands.