Skip to content
This repository has been archived by the owner on Mar 29, 2024. It is now read-only.

Angular 2 Upgrade plan #34

Open
ztl8702 opened this issue Aug 11, 2017 · 4 comments
Open

Angular 2 Upgrade plan #34

ztl8702 opened this issue Aug 11, 2017 · 4 comments

Comments

@ztl8702
Copy link
Member

ztl8702 commented Aug 11, 2017

This will be a long and challenging task. But it is possible and we can do it piece by piece.

First have a look at:
https://angular.io/guide/upgrade

Angular (i.e. Angular 4) can run side by side with AngularJS (i.e. Angular 1). This means that we can write new components in Angular 4 and use them in the old Angular 1 application.

Of course, some configurations and cleaning up are necessary.

@ztl8702
Copy link
Member Author

ztl8702 commented Aug 11, 2017

@rovinglight

@rovinglight
Copy link
Collaborator

👌Seems like we should do that first before other things can go on.

@ztl8702 ztl8702 self-assigned this Aug 30, 2017
@ztl8702 ztl8702 added this to the v2.0 milestone Aug 30, 2017
@ztl8702
Copy link
Member Author

ztl8702 commented Aug 30, 2017

Proposed steps for upgrade:

  1. Configure webpack for module loading. This also prepares for the following step.

  2. Switch to TypeScript. This involves changing all .js files to .ts, and updating gulpfile.js to add TypeScript compilation to the build process.

  3. Change existing views and controllers to Component Directives. This will facilitate the upgrade to Angular 4 as "components" are the primary building blocks in Angular 4.

  4. Switch from ng-app to manual bootstrapping.

After these steps Angular 4 may be introduced into the project.

@ztl8702
Copy link
Member Author

ztl8702 commented Jan 13, 2018

All 4 preparation steps are done. Now kicking off the actual migration.

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

No branches or pull requests

2 participants