In an angular.io project, which files need to be commited to source control?

Issue

I generated an angular project using the command line client (ng-cli). For a basic project, it downloads and builds many different files and folders, including 806 node modules.

├── e2e
├── karma.conf.js
├── node_modules
├── package.json
├── package-lock.json
├── protractor.conf.js
├── README.md
├── src
├── tsconfig.json
└── tslint.json

Which files should be committed to source control?

Solution

As I said in my comment you created your application using angular-cli. By default it will create a .gitignore file that will exclude everything that shouldn't be commit to source control. Currently this file look like:

# compiled output
/dist
/dist-server
/tmp
/out-tsc

# dependencies
/node_modules

# IDEs and editors
/.idea
.project
.classpath
.c9/
*.launch
.settings/
*.sublime-workspace

# IDE - VSCode
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json

# misc
/.sass-cache
/connect.lock
/coverage
/libpeerconnection.log
npm-debug.log
yarn-error.log
testem.log
/typings

# e2e
/e2e/*.js
/e2e/*.map

# System Files
.DS_Store
Thumbs.db

Edit: One can check the current up-to-date version in the angular-cli repository https://github.com/angular/angular-cli/blob/master/packages/schematics/angular/workspace/files/__dot__gitignore.template

Answered By - JEY