GitHub

  • single run: npm run build
  • A simple straight-forward seed for creating Angular Libraries.
  • Ensure you’re running Node ( v4.1.x +) and NPM ( 2.14.x +)
  • $ cd path/to/unzip/folder $ npm install # start the demo server of the seed library $ npm start
  • Now get to work making your library.

angular-library-seed – Get started building an Angular library quickly.

@wwwalkerrun: Build a new exciting Angular lib w/ *ngx* prefix using simple seed: Updated w/ simpler publ…

src chore: update deps – ready for *ngx* prefix Jan 13, 2017

.editorconfig chore: Angular 2 Final updates Sep 26, 2016

.gitignore chore: update deps – ready for *ngx* prefix Jan 13, 2017

.npmignore chore: update deps – ready for *ngx* prefix Jan 13, 2017

CONTRIBUTING.md chore: update deps – ready for *ngx* prefix Jan 13, 2017

LICENSE chore: update deps – ready for *ngx* prefix Jan 13, 2017

PUBLISHING.md chore: update deps – ready for *ngx* prefix Jan 13, 2017

README.md chore: update deps – ready for *ngx* prefix Jan 13, 2017

karma-shim.js chore: Angular 2 Final updates Sep 26, 2016

karma.conf.js chore: update deps – ready for *ngx* prefix Jan 13, 2017

ngx-your-library.ts chore: use ngx prefix Jan 13, 2017

package.json chore: update deps – ready for *ngx* prefix Jan 13, 2017

packagedev.json chore: update deps – ready for *ngx* prefix Jan 13, 2017

packagepublish.json chore: update deps – ready for *ngx* prefix Jan 13, 2017

prep.js chore: update deps – ready for *ngx* prefix Jan 13, 2017

protractor.conf.js chore: Angular 2 Final updates Sep 26, 2016

tsconfig-build.json chore: update deps – ready for *ngx* prefix Jan 13, 2017

tsconfig.json chore: update deps – ready for *ngx* prefix Jan 13, 2017

tslint.json chore: Angular 2 Final updates Sep 26, 2016

typedoc.json chore: update to latest deps, add publishing instructions with setup Dec 10, 2016

webpack.config.js chore: update deps – ready for *ngx* prefix Jan 13, 2017

when debugging or first writing test suites, you may find it helpful to try out Protractor commands without starting up the entire test suite. You can do this with the element explorer.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

GitHub