valor-software/angular2-webpack-starter

Name: angular2-webpack-starter

Owner: Valor Software

Description: An Angular 2 Starter kit featuring Angular 2 (Router, Http, Forms, Services, Tests, E2E, Dev/Prod), Karma, Protractor, Jasmine, Istanbul, TypeScript, TsLint, Codelyzer, Hot Module Replacement, Typings, and Webpack by @AngularClass

Forked from: gdi2290/angular-starter

Created: 2016-03-31 20:29:19.0

Updated: 2017-11-20 13:11:58.0

Pushed: 2016-03-31 20:32:34.0

Homepage: https://angularclass.github.io/angular2-webpack-starter/

Size: 2189

Language: JavaScript

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

taylor swift volkswagen status GitHub version Dependency Status Issue Stats Issue Stats Stack Share

Webpack and Angular 2

Angular2 Webpack Starter Join Slack Join the chat at https://gitter.im/angularclass/angular2-webpack-starter

An Angular 2 starter kit featuring Angular 2 (Router, Forms, Http, Services, Tests, E2E), Karma, Protractor, Jasmine, Istanbul, TypeScript, Typings, TsLint, Codelyzer, Hot Module Replacement, and Webpack by AngularClass.

If you're looking for Angular 1.x please use NG6-starter
If you're looking to learn about Webpack and ES6 Build Tools check out ES6-build-tools
If you're looking to learn TypeScript see TypeStrong/learn-typescript
If you're looking for Webpack 2 version then see the experimental version angular2-webpack2-starter that will be merged

This seed repo serves as an Angular 2 starter for anyone looking to get up and running with Angular 2 and TypeScript fast. Using a Webpack for building our files and assisting with boilerplate. We're also using Protractor for our end-to-end story and Karma for our unit tests.

Quick start

Make sure you have node version >= 4.0

Clone/Download the repo then edit app.ts inside /src/app/app.ts

one our repo
depth 1 removes all but one .git commit history
clone --depth 1 https://github.com/angularclass/angular2-webpack-starter.git

ange directory to our repo
ngular2-webpack-starter

d required global libraries
install typings webpack-dev-server rimraf webpack -g

stall the repo with npm
install

art the server
start

e Hot Module Replacement
run server:dev:hmr

go to http://0.0.0.0:3000 or http://localhost:3000 in your browser

Nitrous Quickstart

You can quickly create a free development environment to get started using this starter kit in the cloud on Nitrous:

Nitrous Quickstart

Simply run HOST=0.0.0.0 npm start from the terminal inside of ~/code/angular2-webpack-starter and access your site via the “Preview > 3000” link in the IDE.

Table of Contents

File Structure

We use the component approach in our starter. This is the new standard for developing Angular apps and a great way to ensure maintainable code by encapsulation of our behavior logic. A component is basically a self contained app usually in a single file or a folder with each concern as a file: style, template, specs, e2e, and component class. Here's how it looks:

lar2-webpack-starter/
config/                    * our configuration
 ???helpers.js             * helper functions for our configuration files
 ???spec-bundle.js         * ignore this magic that sets up our angular 2 testing environment
 ???karma.conf.js          * karma config for our unit tests
 ???protractor.conf.js     * protractor config for our end-to-end tests
 ???webpack.dev.js         * our development webpack config
 ???webpack.prod.js        * our production webpack config
 ???webpack.test.js        * our testing webpack config

src/                       * our source files that will be compiled to javascript
 ???main.browser.ts        * our entry file for our browser environment
 ?
 ???index.html             * Index.html: where we generate our index page
 ?
 ???polyfills.ts           * our polyfills file
 ?
 ???vendor.ts              * our vendor file
 ?
 ???app/                   * WebApp: folder
 ?   ???app.spec.ts        * a simple test of components in app.ts
 ?   ???app.e2e.ts         * a simple end-to-end test for /
 ?   ???app.ts             * App.ts: a simple version of our App component components
 ?
 ???assets/                * static assets are served here
     ???icon/              * our list of icons from www.favicon-generator.org
     ???service-worker.js  * ignore this. Web App service worker that's not complete yet
     ???robots.txt         * for search engines to crawl your website
     ???human.txt          * for humans to know who the developers are


tslint.json                * typescript lint config
typedoc.json               * typescript documentation generator
tsconfig.json              * config that webpack uses for typescript
typings.json               * our typings manager
package.json               * what npm uses to manage it's dependencies

Getting Started

Dependencies

What you need to run this app:

Once you have those, you should install these globals with npm install --global:

Installing
Running the app

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/).

server
velopment
run server
oduction
run build:prod
run server:prod
Other commands
build files
velopment
run build:dev
oduction
run build:prod
hot module replacement
run server:dev:hmr
watch and build files
run watch
run tests
run test
watch and run our tests
run watch:test
run end-to-end tests
ke sure you have your server running in another terminal
run e2e
run webdriver (for end-to-end)
run webdriver:update
run webdriver:start
run Protractor's elementExplorer (for end-to-end)
run webdriver:start
 another terminal
run e2e:live

Configuration

Configuration files live in config/ we are currently using webpack, karma, and protractor for different stages of your application

Contributing

You can include more examples as components but they must introduce a new concept such as Home component (separate folders), and Todo (services). I'll accept pretty much everything so feel free to open a Pull-Request

TypeScript

To take full advantage of TypeScript with autocomplete you would have to install it globally and use an editor with the correct TypeScript plugins.

Use latest TypeScript compiler

TypeScript 1.7.x includes everything you need. Make sure to upgrade, even if you installed TypeScript previously.

install --global typescript
Use a TypeScript-aware editor

We have good experience using these editors:

Typings

When you include a module that doesn't include Type Definitions inside of the module you need to include external Type Definitions with Typings

Use latest Typings module
install --global typings
Custom Type Definitions

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 typings

ngs install node --save

If you can't find the type definition in the registry we can make an ambient definition in this file for now. For example

are module "my-module" {
port function doesSomething(value: string): string;

If you're prototyping and you will fix the types later you can also declare it as type any

are var assert: any;

If you're importing a module that uses Node.js modules which are CommonJS you need to import as

rt * as _ from 'lodash';

You can include your type definitions in this file until you create one for the typings registry see typings/registry

Frequently asked questions

Support, Questions, or Feedback

Contact us anytime for anything about this repo or Angular 2


enjoy ? AngularClass



AngularClass

AngularClass

Learn AngularJS, Angular 2, and Modern Web Development from the best. Looking for corporate Angular training, want to host us, or Angular consulting? patrick@angularclass.com

License

MIT


This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.