-
Notifications
You must be signed in to change notification settings - Fork 18
FAQ
This starter is not created to compete with official CLI and I recommend you to try Angular CLI. I made the starter with similar structure to ease migration.
For those who're new to Angular and tooling, then CLI is for you, no other reason.
For those who're already experienced in Angular, and love to craft-your-own, customize, eager to update packages as soon as it's out, then starters are more suitable for you.
Simple.
Clone is only for collaborators since they need .git
history, or you need specific branch.
Download is for general purpose use.
Download from releases page is highly recommended.
The starter is ready for production bundling using AoT compilation, Lazy-loading, and Tree-shaking support.
It also supports CI/CD pipeline by installing dependencies only needed during test and build.
- You can import them in
src/vendor.ts
andsrc/vendor-style.ts
for CSS
// Pre-included example
import 'bootstrap/dist/css/bootstrap.css';
import 'font-awesome/css/font-awesome.css';
- If you want the package (modular/global) to be cached with DLL, add them to
src/vendor.dll.ts
- Consider running
npm run build:dll
to refresh DLL package
-
Just do
npm install --save <package-name>
-
Install the typing with
npm install -D @types/<package-name>
-
Then just import the package in your TypeScript file
// Example import { filter } from 'lodash';
Yes, you can remove these since it's only used for starter CI:
- .env.travis
- .travis.yml
- appveyor.yml
This starter may not fit for your workflow, since it's opinionated. Therefore you can always fork and custom it to fit your workflow
⭐ Support this starter by giving stars, sharing to your friends, or contributing