Skip to content
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

Unable to install taiko using npm install -g taiko #2645

Open
Shivkant-Chauhan opened this issue Oct 8, 2022 · 1 comment
Open

Unable to install taiko using npm install -g taiko #2645

Shivkant-Chauhan opened this issue Oct 8, 2022 · 1 comment

Comments

@Shivkant-Chauhan
Copy link

Shivkant-Chauhan commented Oct 8, 2022

Describe the bug
I am unable to install taiko on my mac 12.6
Also getting same error on a linux machine.
I have tried installing taiko using various commands like:
sudo npm install -g taiko
sudo TAIKO_SKIP_CHROMIUM_DOWNLOAD=true npm install -g taiko
but unable to do so!

I want to add that the problem is only with mac users.. after installing taiko with sudo npm i -g taiko command, then also I am getting taiko command not found!

Logs

npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm ERR! code 190
npm ERR! git dep preparation failed
npm ERR! command /usr/local/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/Users/shivkantchauhan/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run
npm ERR! npm WARN using --force Recommended protections disabled.
npm ERR! npm ERR! code ENOTEMPTY
npm ERR! npm ERR! syscall rename
npm ERR! npm ERR! path /Users/shivkantchauhan/.npm-global/lib/node_modules/taiko
npm ERR! npm ERR! dest /Users/shivkantchauhan/.npm-global/lib/node_modules/.taiko-0MR00Ccl
npm ERR! npm ERR! errno -66
npm ERR! npm ERR! ENOTEMPTY: directory not empty, rename '/Users/shivkantchauhan/.npm-global/lib/node_modules/taiko' -> '/Users/shivkantchauhan/.npm-global/lib/node_modules/.taiko-0MR00Ccl'
npm ERR!
npm ERR! npm ERR! A complete log of this run can be found in:
npm ERR! npm ERR!     /Users/shivkantchauhan/.npm/_logs/2022-10-08T19_34_00_565Z-debug-0.log

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/shivkantchauhan/.npm/_logs/2022-10-08T19_32_25_945Z-debug-0.log

and

npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated

changed 690 packages, and audited 691 packages in 8s

113 packages are looking for funding
  run `npm fund` for details

9 vulnerabilities (2 moderate, 6 high, 1 critical)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

Expected behavior
Taiko should be installed without any vulnerabilities

Screenshots
Screenshot 2022-10-05 at 6 27 26 PM

output of gauge -v

Gauge version: 1.4.3
Plugins
-------
html-report (4.1.4)
js (2.4.0)
screenshot (0.1.0)
ts (0.1.0)
@marques-work
Copy link
Contributor

marques-work commented Dec 3, 2022

@Shivkant-Chauhan Sorry for the late reply - it might be some issue with your system PATH?

  • are you using a version manager? (e.g., nodenv, nvm, asdf)
  • what does type -a node output?
  • does npx taiko work?

I've tried this on my mac (12.6.1) and on debian bullseye. Couldn't reproduce (installed taiko 1.3.5).

The vulnerabilities are reduced in 1.3.5, but they cannot all be resolved because there are transitive dependencies (related to generating documentation) that rely on vulnerable packages, and until those are updated, there's nothing we can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants