Uploaded image for project: 'Alloy'
  1. Alloy
  2. ALOY-1612

CLI: Be able to use Alloy source-maps in Safari Debugger / Chrome Dev-Tools

    Details

    • Sprint:
      2018 Sprint 07 Tooling

      Description

      Based on a recent discussion with Chris Bowley! Currently, when debugging Alloy in Safari / Chrome, the dev-experience is pretty bad, because the developer sees the generated spaghetti code instead of the actual Alloy code. But there is help! We generate proper source-maps already (look into build/map/*, but it seems like they are not actively used. In addition, it seems like they are indeed used during compile time - for compilation errors when using Babel, where they are doing a great job in indicating the actual line number and character of the error.

      If we could adapt source-maps to the Safari- and Chrome-debugger, we could enable a whole new debugging experience, e.g. by integrating it into our editor plugins and be able to create web-based debuggers like some others do.

      Thoughts welcome!

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cwilliams Christopher Williams
                Reporter:
                hknoechel Hans Knöchel
                Reviewer:
                Ewan Harris
                Tester:
                Satyam Sekhri
              • Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Backbone Issue Sync

                  • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                    Git Source Code