crimson-med / d2i-reader Goto Github PK

PS S:\Repositories\Node\d2i-reader> npm i d2i-reader
npm ERR! code 1
npm ERR! git dep preparation failed
npm ERR! command C:\Program Files\nodejs\node.exe C:\Users\Josh\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js install --force --cache=C:\Users\Josh\AppData\Local\npm-cache --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 WARN registry No auth for URI, but auth present for scoped registry.
npm ERR! npm WARN registry
npm ERR! npm WARN registry URI: https://npm.pkg.github.com/argus-inc/@types/node/-/node-14.0.13.tgz
npm ERR! npm WARN registry Scoped Registry Key: //registry.npmjs.org/
npm ERR! npm WARN registry
npm ERR! npm WARN registry More info here: https://github.com/npm/cli/wiki/No-auth-for-URI,-but-auth-present-for-scoped-registry
npm ERR! npm ERR! code E403
npm ERR! npm ERR! 403 403 Forbidden - GET https://npm.pkg.github.com/argus-inc/@types/node/-/node-14.0.13.tgz - Permission denied
npm ERR! npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! npm ERR! 403 on a server you do not have access to.
npm ERR!
npm ERR! npm ERR! A complete log of this run can be found in: C:\Users\Josh\AppData\Local\npm-cache\_logs\2023-05-25T16_43_49_927Z-debug-0.log

npm ERR! A complete log of this run can be found in: C:\Users\Josh\AppData\Local\npm-cache\_logs\2023-05-25T16_43_39_810Z-debug-0.log