Setup for local development
The
Setting up a new project on your machine is quick and easy with the QuickStart seed, maintained on github.
Make sure you have node and npm installed.
Clone
Perform the clone-to-launch steps with these terminal commands.
git clone https://github.com/angular/quickstart.git quickstart
cd quickstart
npm install
npm start
npm start
fails in Bash for Windows in versions earlier than the Creator's Update (April 2017).
Download
Download the QuickStart seed and unzip it into your project folder. Then perform the remaining steps with these terminal commands.
cd quickstart
npm install
npm start
npm start
fails in Bash for Windows in versions earlier than the Creator's Update (April 2017).
Delete non-essential files (optional)
You can quickly delete the non-essential files that concern testing and QuickStart repository maintenance
(including all git-related artifacts such as the .git
folder and .gitignore
!).
Do this only in the beginning to avoid accidentally deleting your own tests and git setup!
Open a terminal window in the project folder and enter the following commands for your environment:
OS/X (bash)
xargs rm -rf < non-essential-files.osx.txt
rm src/app/*.spec*.ts
rm non-essential-files.osx.txt
Windows
for /f %i in (non-essential-files.txt) do del %i /F /S /Q
rd .git /s /q
rd e2e /s /q
What's in the QuickStart seed?
The QuickStart seed contains the same application as the QuickStart playground. But its true purpose is to provide a solid foundation for local development. Consequently, there are many more files in the project folder on your machine, most of which you can learn about later.
Focus on the following three TypeScript (.ts
) files in the /src
folder.
All guides and cookbooks have at least these core files. Each file has a distinct purpose and evolves independently as the application grows.
Files outside src/
concern building, deploying, and testing your app.
They include configuration files and external dependencies.
Files inside src/
"belong" to your app.
Add new Typescript, HTML and CSS files inside the src/
directory, most of them inside src/app
,
unless told to do otherwise.
The following are all in src/
File | Purpose |
---|---|
app/app.component.ts
|
Defines the same |
app/app.module.ts
|
Defines |
main.ts
|
Compiles the application with the JIT compiler and
bootstraps
the application's main module ( |
Next Step
If you're new to Angular, we recommend you follow the tutorial.
Appendix: node and npm
Node.js and npm are essential to modern web development with Angular and other platforms. Node powers client development and build tools. The npm package manager, itself a node application, installs JavaScript libraries.
Get them now if they're not already installed on your machine.Verify that you are running node v4.x.x
or higher and npm 3.x.x
or higher
by running the commands node -v
and npm -v
in a terminal/console window.
Older versions produce errors.
We recommend nvm for managing multiple versions of node and npm. You may need nvm if you already have projects running on your machine that use other versions of node and npm.
Appendix: Why develop locally
Links on almost every documentation page open completed samples in the browser. You can play with the sample code, share your changes with friends, and download and run the code on your own machine.
The QuickStart shows just the AppComponent
file.
It creates the equivalent of app.module.ts
and main.ts
internally for the playground only.
so the reader can discover Angular without distraction.
The other samples are based on the QuickStart seed.
As much fun as this is ...
- you can't ship your app in Stackblitz
- you aren't always online when writing code
- transpiling TypeScript in the browser is slow
- the type support, refactoring, and code completion only work in your local IDE
Use the
For real development, we strongly recommend developing locally.
Appendix: develop locally with IE
If you develop angular locally with ng serve
, there will be websocket
connection being setup automatically between browser and local dev server, so when your code change, browser can automatically refresh.
In windows, by default one application can only have 6 websocket connections, MSDN WebSocket Settings.
So if IE was refreshed manunally or automatically by ng serve
, sometimes, the websocket will not close properly, when websocket connections exceed limitations, SecurityError
will be thrown, this error will not affect the angular application, you can just restart IE to clear this error, or modify the windows registry to update the limitations.