Skip to content

Improve/Create build process for lib #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dalestone opened this issue Feb 18, 2017 · 3 comments
Closed

Improve/Create build process for lib #26

dalestone opened this issue Feb 18, 2017 · 3 comments

Comments

@dalestone
Copy link
Owner

No description provided.

@11joselu
Copy link

11joselu commented Feb 18, 2017

angular-cli current situation for build components as library

Reference to feature (boilerplate for library): Feature Create boilerplate for library · Issue #1692 · angular/angular-cli

To do

  • Migration from Webpack build system to Gulp
  • Create a new scripts in package.json
  • Create a new tsconfig.json
  • Create a configuration for typescript lint (tslint.json)
  • Create and configure .gitignore, .npminore etc.
  • Create a main file
  • Default export for compatibility with angular cli see
  • Add support for types
  • Webpack configuration to show demo page.
  • Css/Sass configuration
  • Template import or bundle
  • Exclude external libs from main file
  • Build for system compatibility
  • Build for cjs compatibility
  • e2e scripts
  • Test scripts

I will keep updating this list Scratch this.

@11joselu
Copy link

11joselu commented Mar 3, 2017

Brief summary.

First of all I am sorry for possibles English errors (not my native language)

I tried to adapt Webpack configuration for bundle multiples files, inlines resources and compile sass files into separated files, with no great results. After looking some plugins and theirs architecture, I changed from Webpack to Gulp.js using Typescript.

Working repo

This build process, compile TS files into CommonJs module format, inject inline resources (Sass (compiled), HTML), and create a build folder with all js files and css (currently I'm not copying all src files).

What next's?

  • Working on testing

@dalestone
Copy link
Owner Author

Ok looking good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants