Different Aurelia CLI project structure than aurelia/skeleton-navigation

Question

I used the start kit to build my app before Aurelia was released from here : https://github.com/aurelia/skeleton-navigation

But when Aurelia was released , I wanted to check the au new --myApp and it has different structure and build methods than the skeletions.

What is the best way to go with , stay with the skeleton template or move to the CLI one .

Thanks...

Answer 1

Bit of a late answer on this one (but the right time). The Aurelia CLI is quite stable now and supports generating applications using Javascript and Typescript, with the choice of RequireJS or System.js (Webpack support is coming soon).

The difference between the skeletons and CLI projects is as follows:

Skeletons

The skeletons are kitchen sink examples showcasing testing, routing, working with an API and come with additional libraries like Bootstrap and Font Awesome. The skeletons are also the only choice currently (as of July 2017) if you want to use Webpack, but the CLI is going to support Webpack at a later date.

Aurelia CLI

The CLI is a clean starting base that lets you make your own choices like; if you want testing, what code editor you use and so on. The resulting project structure has no routing configured, no examples of fetching data from an API or anything else that you get in the skeletons. The CLI project when you first run it will just display, "Hello world" and nothing more.

If you're confident working with the documentation and like the idea of building up your applications from nothing, then the CLI is for you. You also get the convenience of generator functions which allow you to quickly bootstrap new custom elements, components, value converters and so on.