The goal of this project is to get better at Angular2 , TypeScript and RxJS . I have a background on multiple projects with both Angular1 andReact (with Redux), using Babel / Webpack and other tools.
To bootstrap this project, I’ve used my own boilerplate topheman/webpack-babel-starter that I have adapted from Babel / Eslint to TypeScript / TSLint .
This is still a work in progress. At this time, I’ve released an example of state management via@ngrx/store (a redux-like in RxJS), coupled with RxJS Observable streams wired to Angular2 components . The next step will be to add some network requests involved.
I’ve kept the development workflow exactly the same as topheman/webpack-babel-starter ‘s (build tasks, deployment …).
What’s in there ?
- Development / Build / Lint tasks
- TypeScript transpiler
- Angular2 /RxJS /@ngrx/store
- Sass support
- Ship a version of your site with sourcemaps (see demo)
git clone https://github.com/topheman/angular2-sandbox.git cd angular2-sandbox npm install
If you need to access from a remote device (such as a smartphone on the same network), just
LOCALHOST=false npm start and your site will be accessible via your IP (which will be output on the terminal at launch).
./build directory is ignored by git, it will contain a
dist directory which holds the distribution version of your website (the one that you will ship once built ( more infos on topheman/webpack-babel-starter ).
All the build tasks will create a built version of the project in the
./build/dist folder, cleaning it before making the build.
npm run build
npm run build-prodoptimized / uglified version
npm run build-prod-allwill build:
- production version (optimized / uglified)
- a debuggable version accessible at
/devtoolsshipping all the sourcemaps, to ease sharing transpiled source code
npm run serve-dist will serve your
./build/dist folder at http://localhost:3000 so that you could test the built version you just made.
- tslint is running while you’re developping, check your console for errors
- you can also launch it via
npm run lint
tslint.jsonfor the configuration, inspired by AngularClass/angular2-webpack-starter ‘s
You can customize the behavior of the scripts by specifying environments vars:
NODE_ENVby default at
npm run build-prod
LINTER=falsewill disable the linter (enabled by default, ex:
LINTER=false npm start)
stats.jsonprofiling file on disk from webpack at build (disabled by default, ex:
STATS=true npm run build)
FAIL_ON_ERROR=truewill break the build if any errors occurs (useful for CIs such as travis – at
falsein dev-server, at
LOCALHOST=falseto access via IP from other devices on the same network (ex:
LOCALHOST=false npm start– default
DEVTOOLS: By default at
null. Used internally by
npm run build-prod-all(you may not need that if you don’t do OSS)
More infos about the workflow on topheman/webpack-babel-starter (slight difference: this project uses TypeScript / TSLint over Babel / ESLint
Copyright 2016 © Christophe Rosset
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. The Software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the Software.