* trying Circle CI v2
* paths are fun
* seeing how long a demos build takes
* Batching Demo builds
* testing demo builds on CI2
* batches count from 0
* ok, looks good. preparing for master branch
* forgot `production=true` flag. let’s test that quick.
* forgot to save the file
* making sure that docs are still copied over to ionic-site in the deploy phase
* getting ready for the PR again
also return empty array so that if the exact folder isn’t matched it
won’t continue to filter and run tests. For example, if you pass
`--f=toolbar/color` it will error because that doesn't exist, but still
tries to run `toolbar/colors`.
- If the e2e test doesn’t exist then throw an error
- Don’t log anything if no tests are being built
- Add concurrency arg to change the number of tests being ran at once
* chore(angular): update to latest stable angular
* chore(deps): update app-scripts
* chore(deps): sw-toolbox
* chore(deps): bump to 1.1.1 app-scripts
* chore(deps): abc order sw-toolbox
* chore(deps): update to angular 2.4.8
* chore(build): pass appNgModule path to app-scripts, make run AoT instead of Prod when using --debug
pass appNgModule path to app-scripts, make run AoT instead of Prod when using --debug
* chore(release): add inquirer to prompt for release
* chore(release): wip get release working again and test
also adds nightly back in
* chore(release): WIP remove commented code
* chore(e2e): WIP to add files needed for app-scripts
* chore(e2e): WIP one e2e test building but with errors
* chore(e2e): move e2e.prod to working with app-scripts
move shared functions into util, add support for debug flag when
running e2e.prod / demos.prod which gets passed to app-scripts
* chore(build): fix app-scripts build for all e2e and demos
* chore(e2e): update ionic-angular import path
* chore(build): update dev paths to work with prod
* chore(e2e): get watch working with e2e prod
* docs(scripts): update README for running e2e and demos
closes#8411closes#10023
* chore: fix incorrect execution of node binaries
* Currently gulp runs the `ngc` by manually calling the `./node_modules/.bin/ngc` file (by assuming it's a node script)
This is not always correct, because often package managers like (npm or yarn) create bash files for the package binaries.
* Using `resolve-bin` to properly determine the path to the *real* node script and then we can assume it's a node file.
Fixes#8341
* Remove extra newline
