[ALOY-1725] Use standalone compiler package

GitHub Issuen/a
TypeNew Feature
StatusIn Review
Affected Version/sAlloy 1.14.6
Fix Version/sAlloy 2.0.0
ReporterJan Vennemann
AssigneeJan Vennemann


For Webpack support the Alloy compiler was refactored and moved into a standalone package for easier access in other tooling. This works needs to be folded back into the main Alloy package.


  1. Jan Vennemann 2020-03-04 PR: https://github.com/appcelerator/alloy/pull/952
  2. Ewan Harris 2020-03-06 [~jvennemann], I can't remember how we decided to approach this? Were we initially going to create a next branch and merge the PR to that, and publish under the @next tag on npm? Then I think we could integrate with the appc cli, and publish a pre-release build in production to allow us to try and get some feedback.
  3. Jan Vennemann 2020-03-06 Yes, i think we settled for that. I will have to rebase the PR against that branch then. That way we can maintain the 1.X branch for any bug fixes and go wild on the next branch to get some structure into the repo.
  4. Ewan Harris 2020-03-10 Created the [next branch](https://github.com/appcelerator/alloy/tree/next) and changed the PR to target that. I think it's probably easiest to focus on landing this PR onto next, and then hooking up Jenkins to publish to avoid causing any new conflicts

JSON Source