[ALOY-269] Manage installed version of Alloy
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-09-24T17:52:21.000+0000 |
| Affected Version/s | 2012 Sprint 19 |
| Fix Version/s | 2012 Sprint 19, Release 3.0.0 |
| Components | Titanium SDK, Titanium Studio |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-09-14T09:52:16.000+0000 |
| Updated | 2018-03-07T22:26:02.000+0000 |
Description
Right now TiStudio is simply doing an "npm install alloy" to get alloy. This works for now, but eventually we are going to hit a point where non-backwards-compatible changes are made and developers should be able to manage which version of alloy they would like to install. We need to investigate from an npm perspective how different versions of Alloy can be installed, then we need to see how this can be managed inside TiStudio.
Any version of alloy can be installed globally like this:
and developers can also install locally and execute like this: