au command for bundling app outside of root folder

I’m submitting a feature request

• Library Version: 0.18.0
• Operating System: OSX 10.x
• Node Version: 6.2.2
• NPM Version: 3.9.5
• Browser: all
• Language: all

Current behavior: When running au build all the CLI does is bundle all the assets and put them in the scripts folder. Even if we pass in the env flag with a prod value.

Expected/desired behavior: I would like for the production build command to create a dist folder that has all the assets bundled up along with the index.html file and other file needed to run the application.

What is the motivation / use case for changing the behavior? Deployment. If this was the behavior then deploying an Aurelia app would be very simple specially with services like Firebase that just expect you to pass in your production folder or something like Netlify where they ask what command to run and what the production folder will be.

[threeaccents]

@EisenbergEffect @AStoker I also think you should consider re opening this issue. I understand that everyone has different deployment setups but I think that bundling the app into a dist folder or at least not in the root folder would benefit most aurelia-cli users.

[th3mon]

I created dist task for my project as a gist. You’re welcome 😃!