Future of this project comparing to angular cli?

[asadsahi]

I have been loving this project, but there are few things which I am not clear at the moment:

1. Angular cli is evolving (still not as mature as it has to be), but will we be needing such starter projects. What is the roadmap comparing to cli based projects?

2. Not sure about the purpose of following packages. Are these packages tying us to a specific use case?

"@angularclass/conventions-loader": "^1.0.2",
"@angularclass/hmr": "^1.0.1",
"@angularclass/hmr-loader": "^1.0.1",
"@angularclass/request-idle-callback": "^1.0.7",
"@angularclass/webpack-toolkit": "^1.3.3",

[paralin]

Hot module reload (hmr) for developing faster (no full refresh every change). webpack-toolkit stuff I think was for async reload but we're not sure what the status of that is as of now.

[katallaxie]

@asadsahi

(1) From my experience it is, that most projects are not boilerplate projects, but need a high-level of customization and proprietary solutions. That's when the Starter becomes handy. Because it also captures many of these, either in the code, or in the README.ME.

(2) That is automatically transform Component Metadata to requirestatements, to Hot Module Reloading, and have async components. So, a lot of stuff that is hard to have in the CLI as you have to have a lot of boilerplate code.

[rubenCodeforges]

(2) That is automatically transform Component Metadata to requirestatements, to Hot Module Reloading, and have async components. So, a lot of stuff that is hard to have in the CLI as you have to have a lot of boilerplate code.

ive removed this as it is not required for development, its just a tool and not a strict requirement.
Beside , the readme shows a minimalistic arch but in truth you get whole demo project , witch is not cool for boilerplate - starter kit.

[PatrickJS]

ya I need to remove these packages until I update their useage
"@angularclass/request-idle-callback": "^1.0.7",
"@angularclass/webpack-toolkit": "^1.3.3",
the starter's goal is to make the development workflow as easy as possible for production. I'm also working with the cli team and webpack. The angularclass starter repos will be one of the first repos to be used for a tool we made that we might show off a bit at AngularConnect

[asadsahi]

@gdi2290 is that tool a surprise? Are we expecting an announcement like Angular 2 Team does? :)

Really looking forward for DLL usage with webpack because one of my project rebuilds in roughly 150-250 ms compared to angular2-webpack-starter takes roughly 1-1.5 seconds on same machine. That project uses DLL concept from webpack to skip vendor files. Credit to @SteveSandersonMS 's generator what this project is based on.

[fxck]

This repo will hopefully include DLL as well.. one day.

Things I would really like to see:

1. DLL(update to rc.5 #843 (comment))
2. integrated AOT commands (there are some efforts at this repo https://github.com/qdouble/angular2webpack2-starter)
3. tidying up of configs and the build system generally, now that it's using webpack2 and you can actually use es6 everywhere... CLI has got pretty nice webpack configs for example(use class for config generation #910)

[PatrickJS]

@rubenCodeforges I don't use windows

[rubenCodeforges]

@asadsahi do you use windows ?

[asadsahi]

@rubenCodeforges yes I only use windows, is everything ok??? :)

[rubenCodeforges]

@asadsahi just asking because youve mentioned dll , on unix we dont have them

[asadsahi]

@rubenCodeforges dll is a concept in webpack too. This is to do with having more performance out of webpack.

[fxck]

@gdi2290 could you reply to this #968 (comment) please? What's the current situation with this repo now that angular2 is out? Are you busy preparing for conferences or something? Could we do something to help coordinate effort of updating and tidying up this repo? I know it interests a lot of people. :)

Thank you.

cc @DzmitryShylovich

[fxck]

Hello? @katallaxie @gdi2290

[mikeumus]

Considering becoming an Angular CLI template or using @ngtools/webpack

With the Angular CLI becoming so powerful and central to workflow, it's a good time to consider if this starter makes sense to work as an Angular CLI template. See "App Creation Using Template" in the CLI wiki. Becoming a template would look something like this for a user to get started:

ng new my-ng2-app --template=angular2-webpack-starter

Or adopting @ngtools/webpack to not miss out on any of the innovations happening on the CLI like "code splitting" (see below) and other optimizations.

See the benefits and ability to use @ngtools/webpack standalone from the Angular CLI as presented in Stephen Fluin's Angular CLI talk at Angular Connect 2016:

• Compiles SCSS/LESS
• TypeScript transpilation
• Bundles JavaScript, CSS
• Asset optimization
• Virtual filesystem for assets
  • For serving local assets and compile versions.
• Live-reload via websockets
• Code splitting
  • Recognizing the use of loadChildren in the router, and bundling those modules separately so that any dependencies of those modules are not going to be loaded as part of your main bundle. These separate bundles will be pulled out of the critical path of your application, making your total application bundle much smaller and loading it much more performant.

[PatrickJS]

The next change to the repo would diverge from the current folder structure and the current style guide with the focus on production apps. The change would also include AoT, DLL only for dev and SCSS (since it's the most popular one). Anything the CLI has will be included plus more depending on the opinions and style guide of @AngularClass. The only problem right now is finding the weekend to work on it or start training maintainers for future updates. The CLI and starter repos have different goals which is why this repo will always exist.

[admosity]

Any news on this front? I am using this in a large corporate setting and would be willing to maintain and backport some of my enhancements over. I have gone this route because of the blackbox nature of angular-cli being too risky. I have seen the intake of issues and PRs have slowed, for example: #1640, #1637 should have been merged already.

Some enhancements I currently have:

• Frontend app config
• Commitizen
• Standard changelog
  
• Separate IE polyfill and IE stylesheet bundle
  
• Angular 4
• Custom includePaths setup with scss so components can consume a common import
  Example: feat(sass resolve paths) angular/angular-cli#2747 (comment)
• Postcss/autoprefixer
• Headless protractor and karma configuration via PhantomJS

[PatrickJS]

updates will be in the same issue here #1686