Make sure you have Node version >= 6.0 and NPM >= 3
- File Structure
- Getting Started
- Configuration
- AoT Don'ts
- External Stylesheets
- Contributing
- TypeScript
- @Types
- Frequently asked questions
- Support, Questions, or Feedback
- Deployment
- License
What you need to run this app:
node
andnpm
(brew install node
)- Ensure you're running the latest versions Node
v6.x.x
+ (orv7.x.x
) and NPM3.x.x
+
If you have
nvm
installed, which is highly recommended (brew install nvm
) you can do anvm install --lts && nvm use
in$
to run with the latest Node LTS. You can also have thiszsh
done for you automatically
Once you have those, you should install these globals with npm install --global
:
webpack
(npm install --global webpack
)webpack-dev-server
(npm install --global webpack-dev-server
)karma
(npm install --global karma-cli
)protractor
(npm install --global protractor
)typescript
(npm install --global typescript
)
After you have installed all dependencies you can now run the app. Run npm run server
to start a local server using webpack-dev-server
which will watch, build (in-memory), and reload for you. The port will be displayed to you as http://0.0.0.0:3000
(or if you prefer IPv6, if you're using express
server, then it's http://[::1]:3000/
).
# development
npm run server
# production
npm run build:prod
npm run server:prod
# development
npm run build:dev
# production (jit)
npm run build:prod
# AoT
npm run build:aot
npm run server:dev:hmr
npm run watch
npm run build:docker
Configuration files live in config/
we are currently using webpack, karma, and protractor for different stages of your application
The following are some things that will make AoT compile fail.
- Don’t use require statements for your templates or styles, use styleUrls and templateUrls, the angular2-template-loader plugin will change it to require at build time.
- Don’t use default exports.
- Don’t use
form.controls.controlName
, useform.get(‘controlName’)
- Don’t use
control.errors?.someError
, usecontrol.hasError(‘someError’)
- Don’t use functions in your providers, routes or declarations, export a function and then reference that function name
- @Inputs, @Outputs, View or Content Child(ren), Hostbindings, and any field you use from the template or annotate for Angular should be public
To take full advantage of TypeScript with autocomplete you would have to install it globally and use an editor with the correct TypeScript plugins.
TypeScript 2.1.x includes everything you need. Make sure to upgrade, even if you installed TypeScript previously.
npm install --global typescript
We have good experience using these editors:
- Visual Studio Code
- Webstorm 10
- Atom with TypeScript plugin
- Sublime Text with Typescript-Sublime-Plugin
When you include a module that doesn't include Type Definitions inside of the module you can include external Type Definitions with @types
i.e, to have youtube api support, run this command in terminal:
npm i @types/youtube @types/gapi @types/gapi.youtube
In some cases where your code editor doesn't support Typescript 2 yet or these types weren't listed in tsconfig.json
, add these to "src/custom-typings.d.ts" to make peace with the compile check:
import '@types/gapi.youtube';
import '@types/gapi';
import '@types/youtube';
When including 3rd party modules you also need to include the type definition for the module if they don't provide one within the module. You can try to install it with @types
npm install @types/node
npm install @types/lodash
If you can't find the type definition in the registry we can make an ambient definition in this file for now. For example
declare module "my-module" {
export function doesSomething(value: string): string;
}
If you're prototyping and you will fix the types later you can also declare it as type any
declare var assert: any;
declare var _: any;
declare var $: any;
If you're importing a module that uses Node.js modules which are CommonJS you need to import as
import * as _ from 'lodash';
- What's the current browser support for Angular?
- Please view the updated list of browser support for Angular 2
- Why is my service, aka provider, is not injecting parameter correctly?
- Please use
@Injectable()
for your service for typescript to correctly attach the metadata (this is a TypeScript problem)
- Please use
- Where do I write my tests?
- You can write your tests next to your component files. See
/src/app/home/home.component.spec.ts
- You can write your tests next to your component files. See
- How do I start the app when I get
EACCES
andEADDRINUSE
errors?- The
EADDRINUSE
error means the port3000
is currently being used andEACCES
is lack of permission for webpack to build files to./dist/
- The
- How to use
sass
for css? -
loaders: ['raw-loader','sass-loader']
and@Component({ styleUrls: ['./filename.scss'] })
see Wiki page How to include SCSS in components, or issue #136 for more information.
- How do I test a Service?
- See issue #130
- How do I add
vscode-chrome-debug
support?- The VS Code chrome debug extension support can be done via
launch.json
see issue #144
- The VS Code chrome debug extension support can be done via
- How do I make the repo work in a virtual machine?
- You need to use
0.0.0.0
so revert these changes #205
- You need to use
- What are the naming conventions for Angular?
- How do I include bootstrap or jQuery?
- How do I async load a component?
- Error: Cannot find module 'tapable'
- Remove
node_modules/
and runnpm cache clean
thennpm install
- Remove
- How do I turn on Hot Module Replacement
- Run
npm run server:dev:hmr
- Run
RangeError: Maximum call stack size exceeded
- This is a problem with minifying Angular and it's recent JIT templates. If you set
mangle
tofalse
then you should be good.
- This is a problem with minifying Angular and it's recent JIT templates. If you set
- Why is the size of my app larger in development?
- We are using inline source-maps and hot module replacement which will increase the bundle size.
- If you're in China
- node-pre-gyp ERR in npm install (Windows)
- install Python x86 version between 2.5 and 3.0 on windows see issue #626
Error:Error: Parse tsconfig error [{"messageText":"Unknown compiler option 'lib'.","category":1,"code":5023},{"messageText":"Unknown compiler option 'strictNullChecks'.","category":1,"code":5023},{"messageText":"Unknown compiler option 'baseUrl'.","category":1,"code":5023},{"messageText":"Unknown compiler option 'paths'.","category":1,"code":5023},{"messageText":"Unknown compiler option 'types'.","category":1,"code":5023}]
- remove
node_modules/typescript
and runnpm install typescript@beta
. This repo now uses ts 2.0
- remove
- "There are multiple modules with names that only differ in casing"
- change
c:\[path to angular-starter]
toC:\[path to angular-starter]
see 926#issuecomment-245223547
- change
To run project you only need host machine with operating system with installed git (to clone this repo) and docker and thats all - any other software is not needed (other software like node.js etc. will be automatically downloaded and installed inside docker container during build step based on dockerfile).
brew cask install docker
And run docker by Mac bottom menu> launchpad > docker (on first run docker will ask you about password)
sudo apt-get update
sudo apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
sudo apt-add-repository 'deb https://apt.dockerproject.org/repo ubuntu-xenial main'
sudo apt-get update
apt-cache policy docker-engine
sudo apt-get install -y docker-engine
sudo systemctl status docker # test: shoud be ‘active’
And add your user to docker group (to avoid sudo
before using docker
command in future):
sudo usermod -aG docker $(whoami)
and logout and login again.
Because node.js is big memory consumer you need 1-2GB RAM or virtual memory to build docker image (it was successfully tested on machine with 512MB RAM + 2GB virtual memory - building process take 7min)
Go to main project folder. To build big (~280MB) image which has cached data and is able to FAST rebuild
(this is good for testing or staging environment) type:
docker build -t angular-starter .
To build SMALL (~20MB) image without cache (so each rebuild will take the same amount of time as first build) (this is good for production environment) type:
docker build --squash="true" -t angular-starter .
The angular-starter name used in above commands is only example image name. To remove intermediate images created by docker on build process, type:
docker rmi -f $(docker images -f "dangling=true" -q)
To run created docker image on localhost:8080 type (parameter -p 8080:80
is host:container port mapping)
docker run --name angular-starter -p 8080:80 angular-starter &
And that's all, you can open browser and go to localhost:8080.
If you want to run image as virtual-host on sub-domain you must setup proxy . You should install proxy and set sub-domain in this way:
docker pull jwilder/nginx-proxy:alpine
docker run -d -p 80:80 --name nginx-proxy -v /var/run/docker.sock:/tmp/docker.sock:ro jwilder/nginx-proxy:alpine
And in your /etc/hosts
file (linux) add line: 127.0.0.1 angular-starter.your-domain.com
or in yor hosting add
folowing DNS record (wildchar *
is handy because when you add new sub-domain in future, you don't need to touch/add any DNS record)
Type: CNAME
Hostname: *.your-domain.com
Direct to: your-domain.com
TTL(sec): 43200
And now you are ready to run image on subdomain by:
docker run -e VIRTUAL_HOST=angular-starter.your-domain.com --name angular-starter angular-starter &
docker exec -t -i angular-starter /bin/bash