[ALOY-1733] Add templates for webpack usage
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | None |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2020-08-12T11:22:59.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | CLI Release 8.1.0 |
| Components | Samples & Templates |
| Labels | n/a |
| Reporter | Ewan Harris |
| Assignee | Ewan Harris |
| Created | 2020-07-20T09:56:51.000+0000 |
| Updated | 2020-08-12T11:22:59.000+0000 |
Description
Description
Add templates that work with webpack. At a first glance it appears that the following will be required: * CLI-1393 - needs to be done to allow setting up the initial webpack template from the SDK * -Create new templates in Alloywebpack_default and webpack_two_tabbed- recreate the webpack-default classic app in alloy
* When running alloy new if the provided template starts with (or includes) webpack then we do not add the Alloy plugin to the tiapp
PR: https://github.com/appcelerator/alloy/pull/963
Available in appc CLI 8.1.0-master.9 in preprod
Test steps: 1. Run
appc new --type app --template webpack-default- you should get an app that matches the classic webpack app, but it's alloy and has the alloy dependencies installed*Closing ticket*, verified fix in
8.1.0-master.10, tested using the above test steps.