Alternative lookup convention for `ng-add` schematics

[imhoffd]

It would be nice to be able to externalize schematics from the package specified in the ng add command.

ng add ionic requires us to include schematics within the ionic package itself, which is not ideal for several reasons:

• Separation of Concerns. The ionic package isn't necessarily for Angular, but ng add ionic looks good 👌
• Complication of the build within our main package. Including the schematics in our main package would require including a lot of the Angular DevKit into the build.
• Slow "add". It requires installing the entire package and all its dependencies (~38M) in a sandbox just to use a few files from the package.

In slack I believe we concluded that the best solution might be to have the ng-add field within package.json be allowed to point to another package.

[sebawita]

Yeah, this would be great.
I would love to be able to call ng add nativescript, which could then be redirected to install @nativescript/schematics

[angular-robot]

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]

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.