Repo Update Log

[PatrickJS]

I will be working on updating this repo throughout the coming months. The changes would be a complete rework

New Features

• Angular (4.x.x) latest stable
• Dependencies latest stable
• Webpack latest stable
• TypeScript latest stable
• RxJS latest stable
• zone.js latest stable
• Rename
• Update logo
• Universal-rendering (new by AngularClass) [soon]
• Static-site-rendering (new by AngularClass) [soon]
• Server-side-rendering (new by AngularClass) [soon]
• Client-side-rendering (new by AngularClass) [soon]
• Updated Folder Structure (new AngularClass best practices) [soon]
• Updated Lazy Loading (new AngularClass best practices)
• Updated Webpack Config Design (new by AngularClass) [soon]
• New Task Management System (new by AngularClass) [soon]
• New Ways to Create Initial Repos (new by AngularClass)
• Async Everything
• Updated Support
• Faster Initial Boot
• Better Errors (new by AngularClass)
• New Update Cycle (new by AngularClass)
• New Patterns (new AngularClass patterns)
• New Contributor System (new by AngularClass)
• New Testing System (new by AngularClass)
• HMR everything (not just client-side-rendering) (new by AngularClass)
• environment
• platform

Bonus

• Full-stack
• Migration from Previous Starter
• Initial Service Worker Work (new by AngularClass)
• Deployment Docs (new by AngularClass)

[WillooWisp]

Sounds like a nice list, can't wait to see the result. Will there be an "easy" and straightforward upgrade/merge from previous angular 2 webpack starter setup to this new setup for angular 4?

[PatrickJS]

I'll add the migration as a bonus as the migration is different for everyone

[admosity]

This is great news and this sounds awesome!

I have the same concerns as @WillooWisp. I am using this starter as sort of an upstream repository that maintains the stack maintenance for several downstream applications. The way I have been updating has been via git and projects starting off with a full clone so the history matches up. So I have this sort of setup for maintenance:

angular-webpack-starter -> angular-webpack-starter (opinionated) -> downstream apps

Where the opinionated setup is a fork of the version here with some adjustments for production readiness (postcss autoprefixer, IE specific conditional bundle, dev/prod frontend environment config etc...) and a specific CI/CD setup for a particular client, but still maintaining the same git history.

Sample update from opinionated setup:

Can you outline some of the strategies (or is this available somewhere) that AngularClass will be taking for some of the bigger pieces here? Particularly I am interested in how the webpack configuration would change, how I will need to prepare for this and how can I help out here.

Here's a list of enhancements I've done to the current setup:

• IE conditional bundle and styles
• Frontend environment configuration for dev/prod
• deployUrl functionality from angular cli
• baseUrl functionality from angular cli
• includePaths functionality for sass
  • Component sass architecture (eg: feat(sass resolve paths) angular/angular-cli#2747 (comment))
• Headless testing with PhantomJS, but switching to headless chrome in the future
• Minified index.html for prod build
• commitizen
• standard-changelog support
• angular 4
• tslint fix task
• reusable dependencies for setup compliant library building
  

Some things in my roadmap:

• CLI for generating files compliant with folder structure
• Headless chrome for testing
• a11y testing
• ngrx setup with sensible folder structure
• better checking for catching AoT issues

Just want to say thanks for the amazing project and that this is definitely my preferred choice over some of the starter setups available.

[WillooWisp]

My hope is that the new and upgraded angular 4 supported starter is based on the same repository so that we can merge it in, with some manual merging of course. I have added things like bootstrap 4 loader and font loader for example.

[PatrickJS]

@admosity thank you for providing a lot of great feedback. My plan is to create a repo that can fit your requirements of continuously updating the base starter. With this change, migration in the future would be a lot easier so long as everyone follows the conventions. For migration from the current design to the new, I don't know what the that would look like yet because it depends on everyone's setup after the initial seed. There will be some major refactors such as not using npm-tasks for task management. There will be more helpers for creating new folders and managing the repo in general. A lot of the awesome features aren't on the list and require more time but I'll keep everyone updated :)

The folder structure change would benefit lazy loading more and is slightly different from the current setup. The change would be providing more structure the convention

[WillooWisp]

I really hope this can be part of the existing repo, branch or whatever, so all our existing repos, based on current starter, will continue to be related and so that pull/merge scenarios now and in the future will continue to work easily. Good work!

[Uter1007]

Awesome to hear that this project is still alive. Can't wait to see the new hot sh*t ;)

Cheers & keep up that great work