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

Refusing to install package with name "amazon-chime-sdk-js" #18

Closed
lawrencepit opened this issue Dec 5, 2019 · 1 comment
Closed

Refusing to install package with name "amazon-chime-sdk-js" #18

lawrencepit opened this issue Dec 5, 2019 · 1 comment
Labels
Bug Something isn't working

Comments

@lawrencepit
Copy link

On a fresh Amazon Linux EC2 instance:

[ec2-user@ip-10-0-101-221 ~]$ git clone https://github.com/aws/amazon-chime-sdk-js.git
Cloning into 'amazon-chime-sdk-js'...
remote: Enumerating objects: 262, done.
remote: Counting objects: 100% (262/262), done.
remote: Compressing objects: 100% (190/190), done.
remote: Total 1685 (delta 69), reused 200 (delta 51), pack-reused 1423
Receiving objects: 100% (1685/1685), 838.40 KiB | 1.88 MiB/s, done.
Resolving deltas: 100% (708/708), done.

[ec2-user@ip-10-0-101-221 ~]$ cd amazon-chime-sdk-js/

[ec2-user@ip-10-0-101-221 amazon-chime-sdk-js]$ node -v
v13.3.0

[ec2-user@ip-10-0-101-221 amazon-chime-sdk-js]$ npm -v
6.13.1

[ec2-user@ip-10-0-101-221 amazon-chime-sdk-js]$ npm install amazon-chime-sdk-js --save
npm ERR! code ENOSELF
npm ERR! Refusing to install package with name "amazon-chime-sdk-js" under a package
npm ERR! also called "amazon-chime-sdk-js". Did you name your project the same
npm ERR! as the dependency you're installing?
npm ERR!
npm ERR! For more information, see:
npm ERR!     <https://docs.npmjs.com/cli/install#limitations-of-npms-install-algorithm>

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ec2-user/.npm/_logs/2019-12-05T05_44_16_302Z-debug.log
@lawrencepit lawrencepit added the Bug Something isn't working label Dec 5, 2019
@andi-amzn
Copy link

@lawrencepit, thanks for sharing your console output. It looks like you cloned the repo from source and then tried to install the package from npm into the same repo directory, hence the error. You only need to do one of those depending on what you are trying to do.

If you are looking to run the demos, then you don't need to install from npm. The source checkout has everything you need to run the demos.

You would use npm install if you were to integrate this library into an existing application.

I see now from our README.md that it could be more clear about when to use npm install. I will update this to be more clear about which situations you would want to run npm install.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants