"Autobots, recon."
- Transformers (2007)
Okay. So you got your app running. But before celebrating, let's take a quick peek in our folder and try to make sense of what Angular CLI has built for us.
Your folder would look something like:
Let's tackle these one at a time.
| File/Folder | Purpose |
|---|---|
| .git/ | Used for git version control. |
| e2e/ | Used for end to end test cases by protractor. |
node_modules/ |
Contains your npm packages, as you might know. |
| src/ | This is where your code goes. |
| .editorconfig | IDE formatting stuff. |
| .gitignore | The names of the folders NOT to be committed to git, currently, that's node_modules. |
| angular-cli.json | Angular CLI settings. |
| karma.conf.js | Karma settings for unit tests. |
| package.json | List of npm packages installed. |
| protractor.conf.js | Protractor settings for enn-to-end tests. |
| README.md | Shows up on your app's github page. |
| tslint.json | TypeScript settings |
Note: Unlike some other starter packs, CLI doesn't use Babel to transpile ES6 code to ES5. It's already got TypeScript.
Important
You might have noticed that webpack.config.js is conspicuously absent. Apparently, CLI doesn't trust us not to screw up our webpack configuration. There are workarounds to eject the config file and edit it, should you ever need to do that, but let's not get into all that right now.