The documentation setup procedures install a lot of files. Most of them can be safely ignored.
Application files inside the
e2e/ folders matter most to developers.
Files outside those folders condition the development environment. They rarely change and you may never view or modify them. If you do, this page can help you understand their purpose.
Angular application files go here.
Ships with the "Hello Angular" sample's
End-to-end (e2e) tests of the application, written in Jasmine and run by the protractor e2e test runner.
Initialized with an e2e test for the "Hello Angular" sample.
The npm packages installed with the
Tooling configuration files and folders. Ignore them until you have a compelling reason to do otherwise.
The history of changes to the QuickStart repository. Delete or ignore.
The application icon that appears in the browser tab.
The application host page.
It loads a few essential scripts in a prescribed order.
Then it boots the application, placing the root
A list of files that you can delete if you want to purge your setup of the original QuickStart Seed testing and git maintainence artifacts. See instructions in the optional Deleting non-essential files section. Do this only in the beginning to avoid accidentally deleting your own tests and git setup!
The open source MIT license to use this setup code in your application.
Contains command scripts for running the application,
running tests, and more. Enter
Configuration for the protractor end-to-end (e2e) test runner.
Instruction for using this git repository in your project. Worth reading before deleting.
Global styles for the application. Initialized with an
Tells the SystemJS module loader where to find modules
Don't touch this file unless you are fully versed in SystemJS configuration.
Optional extra SystemJS configuration.
A way to add SystemJS mappings, such as for appliation barrels,
without changing the original
This file defines linting rules favored by the Angular style guide and by the authors of the documentation.