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

Parity: Titanium CommonJS modules require'd differently than NodeJS require spec

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: Release 5.3.0
    • Fix Version/s: Release 6.0.0
    • Component/s: Android, iOS
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      2016 Sprint 12 SDK

      Description

      We have a long-standing issue with how Titanium CommonJS modules are require'd.

      One would assume they'd follow typical NodeJS conventions with requires, so when you do:

      require('module.id');
      

      I would expect that it should attempt to load up modules/commonjs/module.id/<version> as a directory as per TIMOB-23382

      Instead, our Android and iOS implementation looks for modules/commonjs/module.id/<version>/module.id.js, and ignore any package.json, index.js, or index.json in that directory.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cwilliams Christopher Williams
                Reporter:
                cwilliams Christopher Williams
                Reviewer:
                Chee Kiat Ng (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Backbone Issue Sync

                  • Titanium SDK/CLI <> Titanium Mobile
                    Synced with:
                    TIMOB-9743
                    Sync status:
                    ERROR
                    Last received:
                    Last sent:

                    Git Source Code