angular / angular-cli

CLI tool for Angular
https://cli.angular.io
MIT License
26.76k stars 11.97k forks source link

ng add github repository #12263

Open boulix3 opened 6 years ago

boulix3 commented 6 years ago

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ X] feature request

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [X ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

node 8.1.1 npm 5.6.0 Windows 10

Repro steps

ng add https://github.com/boulix3/store-builds doesn't work npm i https://github.com/boulix3/store-builds installs the package from github

The log given by the failure

I've also tried the various syntaxes to add a package listed in this documentation page https://docs.npmjs.com/cli/install such as git:// etc...

Desired functionality

It would be nice to be able to install a package from github and execute the ng-add schematic.

Mention any other details that might be useful

I seems to me that when the ng add command passes the package name to npm, it splits on '/' and only takes the first item (boulix3 the first example, and https: in the second) and passes it to npm.

boulix3 commented 6 years ago

For information, here is the workaround I use

npm i owner/repo-name
ng g package-name:ng-add
angular-robot[bot] commented 2 years ago

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

angular-robot[bot] commented 2 years ago

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.