-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install Speaker node-gyp #114
Comments
Have you tried to execute the following command before installing node-gyp with administrator privileges? That worked for me. |
Perhaps this undocumented dependency should be added to the documentation? |
Node.js v21.6.1 npm ERR! A complete log of this run can be found in: C:\Users\MANUTANU\AppData\Local\npm-cache_logs\2024-02-05T07_50_03_334Z-debug-0.log i keep getting this error plz help |
Hello,
I tried to install speaker, but I cannot because of the following issues:
`C:>node -v
v10.1.0
C:>npm -v
6.1.0
C:\poc>npm install speaker --save
C:\poc\node_modules\speaker>if not defined npm_config_node_gyp (node "C:\Users<username>\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "node C:\Users<username>\AppData\Roaming\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
internal/modules/cjs/loader.js:573
throw err;
^
Error: Cannot find module 'C:\poc\node_modules\speaker\node C:\Users<username>\AppData\Roaming\npm\node_modules\node-gyp\bin\node-gyp.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:571:15)
at Function.Module._load (internal/modules/cjs/loader.js:497:25)
at Function.Module.runMain (internal/modules/cjs/loader.js:719:10)
at startup (internal/bootstrap/node.js:228:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:576:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! speaker@0.4.1 install:
node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the speaker@0.4.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.`
The text was updated successfully, but these errors were encountered: