Adding features to CLI scaffolding is not that hard. The hard part is to maintain them and test them before every release.
The current CLI offering already causes pressure on e2e tests when release. It took few hours to run through 72 skeletons (yet they didn’t cover the full combinations of all options) on 3 OS. You can imagine fix/re-test cycle is quite slow.
The current “Navigation App” was mainly designed for our CLI release check that runs an app with some code (not just one page hello world). We thought about upgrading the bootstrap v3 to v4 for the navigation app, but didn’t spend time on it so far. We didn’t expect any user to start a real app with this selection, it was more like a demonstration.
The other thing we can do is to enhance documentation to cover the integration with common libs. Aurelia is quite flexible and easy with 3rd-party libs, but we have to show it to new comers.
In Aurelia 2, we are starting with minimum options in scaffolding aurelia/new, will grow them with only essential options. We were talking about offering different level of scaffoldings, the core scaffolding with small set of options but solidly tested, then maybe few more repos for other broader options but to be maintained with the help from the community. No decision is fixed yet for Aurelia 2, we are open to ideas.