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

Implement full NodeJS require specs so we can use NPM for modules

          Details

          • Story Points:
            8
          • Sprint:
            2016 Sprint 14 SDK

            Description

            I know from Jeff Haynie that Hyperloop (and thus Ti.Next - likely Titanium 4.x) will support the full NodeJS require specs so to make it possible to use NPM as a package manager for all kinds of modules. This is also the direction ALOY-86 has been going, asking for widget dependency management.

            I open this ticket to request looking into the possibility of implementing this in Titanium 3.x already.

            • What are the obstacles to change the require implementation to require both JS and native modules from the local and global node_modules paths?
            • What does it take to get Alloy to loading e.g. widgets from local and global installed node_modules?
            • How should the builder copy in global node_modules to the project when it packages the app?

            I think this would spur and new wave of Titanium native/CommonJS modules and Alloy widgets, sync adapters etc that would really boost the platform, as well as making it easier to re-use proprietary components in multiple projects myself.

            Ultimately, I think tiapp.xml and manifest could even be replaced by package.json?

              Attachments

                Issue Links

                relates to

                Epic - gh.issue.epic.desc TIMOB-26570 Node compatibility and developer experience

                • High - Crashes, loss of data, severe memory leak.
                • Open

                New Feature - A new feature of the product, which has yet to be developed. TIMOB-19392 Load JS files and image assets relative to a different codebase than resourcesDirectory

                • None -
                • Open

                Bug - A problem which impairs or prevents the functions of the product. TIMOB-23382 Parity: Cannot require directory as done in NodeJS

                • Critical - Blocks development and/or testing work, production could not run.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. TIMOB-24293 Alloy: iOS - Using require() without "/" prefix will try to load file relatively node_modules first, other unrelated logs and behavior changes

                • Critical - Blocks development and/or testing work, production could not run.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. TIMOB-23138 Parity: On Android require() tries current folder first

                • High - Crashes, loss of data, severe memory leak.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. TIMOB-23543 TiAPI: require implementation uses incorrect __filename values

                • High - Crashes, loss of data, severe memory leak.
                • Closed

                Story - gh.issue.story.desc TIMOB-9893 TiAPI: CommonJS 1.1 compliance

                • High - Crashes, loss of data, severe memory leak.
                • Closed

                New Feature - A new feature of the product, which has yet to be developed. TIMOB-20472 Allow require to find modules in node_modules, etc

                • High - Crashes, loss of data, severe memory leak.
                • Closed

                Improvement - An improvement or enhancement to an existing feature or task. ALOY-1509 Generate spec-compliant require calls

                • High - Crashes, loss of data, severe memory leak.
                • Resolved

                  Activity

                    People

                    • Assignee:
                      cwilliams Christopher Williams
                      Reporter:
                      fokkezb Fokke Zandbergen
                    • Watchers:
                      20 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