-
Notifications
You must be signed in to change notification settings - Fork 669
[Feature Request]: Integrating with angular/cli #2850
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
Comments
@sandangel I took a look at Angular schematics a little while ago and it's not quite ready yet for other players. I'm excited to do some work on our generators, too. See #2407. For 5 -> #2595 As for the rest, I need to investigate the rest a bit more. Perhaps @danbucholtz knows more. |
@dwieeb thanks for your answer. I know that angular schematics is not ready yet, but It will, soon. You can take a look at @nrwl, they had an early adoption of angular/schematics, with experimental feature angular/bazel build tool. This is really amazing. At this time ionic build takes about 15~20s for webpack stuffs. It will be a huge boost for end users, as well as for Ionic Pro cloud build with angular/bazel. Can't wait to see this. |
+1 I'm getting the same warning using the angular-cli in this POC (Code sharing between web and mobile using Ionic only for web) https://github.com/proyecto26/nativescript-ionic-template |
The Ionic CLI will use the Angular CLI for tooling in CLI v4, which supports Ionic Angular v4. The CLI will also continue to support Ionic Angular v2/v3 with |
Excellent news! thanks guys! 👍 |
Uh oh!
There was an error while loading. Please reload this page.
Since angular/cli 1.5, we could use schematics to generate project boilerplate. So I think it is possible to integrate ionic with angular/cli to take the advantages of:
1/ make use of --build-optimizer to reduce bundle size.
2/ using angular/bazel for blazing fast 2s production build which will release about next year.
3/ building web components not only by stencil, but also by brand new angular/elements package.
4/ environment variable support: We don't have to do some workarounds as described in this issue.
5/ optional adding cordova support, If we are building PWA, we won't need cordova.
You can take a look at ngx-rocket. They did a great job but there is still some warning about crucial dependencies in console when serving app.
The text was updated successfully, but these errors were encountered: