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

Alloy uses old require-paths with new require-behavior

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Release 6.2.0, alloy 1.9.11
    • Component/s: Runtime
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      2017 Sprint 07 Tooling

      Description

      We introduced an updated require-handling in Titanium 6 that matches the full NodeJS specs for handling all kind of files and data structures. Although we are save for older require-paths, we should update the Alloy-internal require-calls as well. Example log:

      require called with un-prefixed module id: alloy/constants, should be a core or CommonJS module. Falling back to old Ti behavior and assuming it's an absolute path: /alloy/constants
      

      It will only be shown in the DEBUG log-level, but adjusting it internally would be the cleanest way here. Thx!

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                fmiao Feon Sua Xin Miao
                Reporter:
                hknoechel Hans Knöchel
                Reviewer:
                Hans Knöchel
              • Watchers:
                8 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 Integration