leon
leon copied to clipboard
Error: Cannot find module '/leon/node_modules/stt/lib/binding/v1.4.0/linux-x64/node-v108/stt.node'
Specs
- Leon version: 1.0.0-beta.8+dev
- OS (or browser) version: 5.15.60-1-MANJARO
- Node.js version: v18.4.0
- Complete "leon check" (or "npm run check") output:
> [email protected]+dev check > ts-node scripts/run-check.js ⠋ .: CHECKING :. ℹ️ Leon version ✅ 1.0.0-beta.8+dev ℹ️ node --version ✅ v18.4.0 ℹ️ npm --version ✅ 8.19.1 ℹ️ pipenv --version ✅ pipenv, version 2022.9.8 ℹ️ pipenv --where ✅ /home/dlwxxxdlw/codes/jackdeng/leon/bridges/python ℹ️ pipenv run python --version ✅ Python 3.10.5 ℹ️ pipenv run python bridges/python/main.py scripts/assets/intent-object.json ✅ {"domain": "leon", "skill": "random_number", "action": "run", "lang": "en", "utterance": "Give me a random number", "entities": [], "slots": {}, "output": {"type": "end", "codes": ["49"], "speech": "49", "core": {}, "options": {}}} ℹ️ Global resolvers NLP model state ✅ Found and valid ℹ️ Skills resolvers NLP model state ✅ Found and valid ℹ️ Main NLP model state ✅ Found and valid ℹ️ Amazon Polly TTS ⚠️ Amazon Polly TTS is not yet configured ℹ️ Google Cloud TTS/STT ⚠️ Google Cloud TTS/STT is not yet configured ℹ️ Watson TTS ⚠️ Watson TTS is not yet configured ℹ️ Offline TTS ✅ Found Flite at bin/flite/flite ℹ️ Watson STT ⚠️ Watson STT is not yet configured ℹ️ Offline STT ✅ Found Coqui language model at bin/coqui/huge-vocabulary.scorer .: REPORT :. ℹ️ Here is the diagnosis about your current setup ✅ Run ✅ Run skills ✅ Reply you by texting ⚠️ Amazon Polly text-to-speech ⚠️ Google Cloud text-to-speech ⚠️ Watson text-to-speech ✅ Offline text-to-speech ⚠️ Google Cloud speech-to-text ⚠️ Watson speech-to-text ✅ Offline speech-to-text ✅ Hooray! Leon can run correctly ℹ️ If you have some yellow warnings, it is all good. It means some entities are not yet configured
- (if using Docker) Complete "npm run docker:check" output:
- (optional) Leon skill version:
Expected Behavior
Offline stt can work properly
Actual Behavior
Leon popup the error after npm start
command.
.: STT :.
✅ New instance
ℹ️ Initializing STT...
node:internal/modules/cjs/loader:946
const err = new Error(message);
^
Error: Cannot find module '/home/dlwxxxdlw/codes/jackdeng/leon/node_modules/stt/lib/binding/v1.4.0/linux-x64/node-v108/stt.node'
Require stack:
- /home/dlwxxxdlw/codes/jackdeng/leon/node_modules/stt/index.js
- /home/dlwxxxdlw/codes/jackdeng/leon/server/dist/stt/coqui-stt/parser.js
- /home/dlwxxxdlw/codes/jackdeng/leon/server/dist/stt/stt.js
- /home/dlwxxxdlw/codes/jackdeng/leon/server/dist/core/http-server/server.js
- /home/dlwxxxdlw/codes/jackdeng/leon/server/dist/index.js
at Module._resolveFilename (node:internal/modules/cjs/loader:946:15)
at Module._load (node:internal/modules/cjs/loader:787:27)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object.<anonymous> (/home/dlwxxxdlw/codes/jackdeng/leon/node_modules/stt/index.js:24:17)
at Module._compile (node:internal/modules/cjs/loader:1112:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1166:10)
at Module.load (node:internal/modules/cjs/loader:988:32)
at Module._load (node:internal/modules/cjs/loader:834:12)
at Module.require (node:internal/modules/cjs/loader:1012:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/home/dlwxxxdlw/codes/jackdeng/leon/node_modules/stt/index.js',
'/home/dlwxxxdlw/codes/jackdeng/leon/server/dist/stt/coqui-stt/parser.js',
'/home/dlwxxxdlw/codes/jackdeng/leon/server/dist/stt/stt.js',
'/home/dlwxxxdlw/codes/jackdeng/leon/server/dist/core/http-server/server.js',
'/home/dlwxxxdlw/codes/jackdeng/leon/server/dist/index.js'
]
}
Node.js v18.4.0
How Do We Reproduce?
- Clone leon repo on a Manjaro machine.
- Run
npm run setup:offline
. - Run
npm start
.
Extra (like a sample repo to reproduce the issue, etc.)
There's only node-v102 for [email protected] , don't know why leon asked for node-v108
Hi @JackTheMico, thanks for reporting. Can you please try with a Node.js 16 version? On a side note, Leon requires Python 3.9.10 and you are using 3.10.5.
Tried, popup a new error.
Had the same first error and it disappear after going to node v16.16.0