Differences

This shows you the differences between two versions of the page.

--- dev:browser_staff:angular5 [2017/12/21 11:06] – [Bootstrap 4 Notes] erickson
+++ dev:browser_staff:angular5 [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 20: / Line 20: @@
 ==== Bootstrap 4 Notes ====
-  * Implicit in the move to Ang5 is a move to BS 4.  The Ang5-compatible bootstrap library ng-bootstrap supports BS 4 only.
+  * The Ang5-compatible bootstrap library ng-bootstrap supports BS4 only.
   * Version 4 is mostly backward compatible with version 3.
   * The "panel" is no more -- replaced with "card".
@@ Line 33: / Line 33: @@
 ==== Upgrade Path Recommended by Angular ====
-  - Follow the AngularJS Style Guide
-  - Using a Module Loader
-    - Angular5 (well, ng-cli) uses Webpack by default.
-    - May be implemented independent of any Ang5 upgrade plans.
-    - Can be rolled out in multiple phases.
-      - Phase I: Use webpack as a drop-in replacement for Grunt for compiling builds (and use npm to run karma unit tests).
-        - This is low impact.  No application code changes are required.
-        - I have a branch that does this (plus Angular 1.6 -- TODO: post to LP)
-      - Phase II: Start using ES6-style module 'import' statements for specifying dependencies.
-        - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import
-        - These replace <script/> imports
-  - Migrating to TypeScript
-  - Using Component Directives
-  - Upgrading with ngUpgrade
 See also https://angular-2-training-book.rangle.io/handout/migrate/ng-upgrade/order_of_operations.html
+=== I. Follow the AngularJS Style Guide ===
+=== II. Use a Module Loader ===
+  - Angular5 (well, ng-cli) uses Webpack by default.
+  - May be implemented independent of any Ang5 upgrade plans.
+  - Improved options for creating of JS, etc. bundles
+  - Can be implemented in low-impact phases.
+    - Phase I: Use webpack as a drop-in replacement for Grunt for compiling builds (and use npm to run karma unit tests).
+      - No application code changes are required.
+      - I have a branch that does this (plus Angular 1.6 -- https://bugs.launchpad.net/evergreen/+bug/1739803 [pushed to 3.1-beta])
+    - Phase II: Start using ES6-style module 'import' statements for specifying dependencies.
+      - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import
+      - These ultimately replace <script/> imports
+=== III. Migrating to TypeScript ===
+=== IV. Using Component Directives ===
+=== V. Upgrade with ngUpgrade ===