Uploaded image for project: 'Titanium SDK/CLI'
  1. Titanium SDK/CLI
  2. TIMOB-24980

Allow babel plugins to be added via config.json

    Details

    • Type: Improvement
    • Status: Open
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Alloy 2.0.0
    • Component/s: Tooling
    • Labels:
    • Story Points:
      8
    • Sprint:
      2017 Sprint 17 Tooling, 2017 Sprint 18 Tooling, 2017 Sprint 19 Tooling, 2017 Sprint 20 Tooling, 2017 Sprint 21 Tooling, 2017 Sprint 22 Tooling, 2017 Sprint 23 Tooling, 2017 Sprint 24 Tooling, 2017 Sprint 25 Tooling, 2017 Sprint 26 Tooling, 2018 Sprint 01 Tooling, 2018 Sprint 02 Tooling, 2018 Sprint 03 Tooling, 2018 Sprint 04 Tooling, 2018 Sprint 06 SDK, 2018 Sprint 07 SDK, 2018 Sprint 08 SDK, 2018 Sprint 09 SDK

      Description

      As a developer,
      I want to be able to add/configure babel plugins to run on my code,
      So that I can add features without Alloy pull request.
      

      There are a lot of features that can be added to Alloy by allow babel presets and plugins to be defined in config.json. Currently, it is somewhat possible to add a preset by pushing them to sourceMapper.OPTIONS_OUTPUT.presets from inside alloy.jmk. However, when adding plugins, they are removed because Alloy is overwriting all plugins here: https://github.com/appcelerator/alloy/blob/master/Alloy/commands/compile/index.js#L1131-L1136

      If instead it used _.defaults (or even better, a merge), it could preserve any changes to sourceMapper.OPTIONS_OUTPUT.plugins

        Attachments

          Activity

            People

            • Assignee:
              cwilliams Christopher Williams
              Reporter:
              brentonhouse Brenton House
            • Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:

                Git Source Code