Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TIMOB-26352] Add support for using node_modules from project root directory #950

Closed
wants to merge 7 commits into from

Conversation

brentonhouse
Copy link
Contributor

No description provided.

@brentonhouse brentonhouse changed the title Add support for using node_modules from project root directory [TIMOB-26352] Add support for using node_modules from project root directory Jan 23, 2020
@build
Copy link

build commented Jan 23, 2020

Warnings
⚠️

Please ensure to add a changelog entry for your changes. Edit the CHANGELOG.md file and add your change under the Unreleased items header

Messages
📖

✅ All tests are passing
Nice one! All 3490 tests are passing.

New dependencies added: @titanium/module-copier.

@titanium/module-copier

Author: Brenton House

Description: Copies dependencies defined in package.json to Titanium Resources directory

Homepage: https://github.com/brentonhouse/titanium-module-copier#readme

Created12 months ago
Last Updatedabout 1 month ago
LicenseMIT
Maintainers1
Releases22
Direct Dependenciesfs-extra
Keywordstitanium, mobile, alloy, eslint, turbo, axway, appcelerator, ios, android, iphone, ipad, modules and brenton-house
README

@titanium/module-copier

@titanium/module-copier
Dependabot Status

Turbo is not an official Axway product.
It is an experiment by Brenton House using open-source projects. You are welcome to try it out but be aware of the risks

📝 Description

This module copies dependencies defined in package.json to Titanium Resources directory.

Currently, if you want to be able to use npm to install packages for Titanium, you need to do it from /app/lib, /app/vendor, or /app/assets.

What this module does is it gives the you (the developer) the ability to install Node.js modules for Titanium in the same place you are installing Node.js modules for everything else.

🚀 Getting Started

This module is meant to be used as part of the Titanium mobile build process.

There are several ways this module can be used by Titanium:

  • You can follow this JIRA ticket about this feature getting integrated into Titanium SDK
  • You can use this a part of a Titanium Plugin
  • You can execute this as command-line tool: copymodules <projectPath> <targetPath>

🔗 Related Links

Titanium Mobile - Open-source tool for building powerful, cross-platform native apps with JavaScript.
Alloy - MVC framework built on top of Titanium Mobile.
Appcelerator - Installer for the Appcelerator Platform tool

📚 Learn More

Axway Developer Portal

📣 Feedback

Have an idea or a comment? Join in the conversation here!

©️ Legal

Alloy is developed by Appcelerator and the community and is Copyright © 2012-Present by Appcelerator, Inc. All Rights Reserved.

Alloy is made available under the Apache Public License, version 2. See their license file for more information.

Appcelerator is a registered trademark of Appcelerator, Inc. Titanium is a registered trademark of Appcelerator, Inc. Please see the LEGAL information about using trademarks, privacy policy, terms of usage and other legal information at http://www.appcelerator.com/legal.

Generated by 🚫 dangerJS against c547a50

@sgtcoolguy
Copy link
Contributor

I don't think this is the right location to add support - it'd only work for Alloy apps. Also, it's leading to extra copying (copy from node_modules -> Resources, then "copy" from Resources -> app build dir)

I've started working on this in the SDK itself: tidev/titanium-sdk#11447

@ewanharris
Copy link
Contributor

Closing, as stated by @sgtcoolguy we'll be dealing with this at the SDK level

@ewanharris ewanharris closed this Feb 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants