Tobias Bieniek

That's not the point. We have no way to actually find the right package.json without guessing.

> > That's not the point. We have no way to actually find the right package.json without guessing. > > tell me more if you use ``` ember install "https://github.com/kaliber5/ember-bootstrap#bs4-blueprint"...

I guess we could try to do the right thing by always running `npm install`, checking if a node modules exists with a name matching the repo name and otherwise...

@srvance it will be installed into `node_modules` with the folder name matching the `name` property in the `package.json` file. but to get to the `package.json` file we need the folder...

> Although we could probably have a high hit rate if we try the name parsed out of the URL to reduce the warning occurrence. yeah, that would probably be...

That looks like very private "API" to me and I'd rather not use that. And for yarn this would need yet another approach, so not really a great universal solution.

@les2 that would be a solution, but that's quite a lot of overhead and complexity that I'd rather avoid. we've discussed this in the weekly CLI call yesterday and came...

@srvance this should definitely belong in Ember CLI itself, since we're only *guessing* the project name.

@villander I totally agree and you're very welcome to contribute to the existing documentation :)

FWIW it seems that https://pnpm.io is a much easier way to achieve the same goals and aside from ember-cli not supporting it officially yet it works quite well :)