Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-9017] Tooling: JavaScript files under the resource directory of a project are compiled into the binary. There should be a way to include *.js files in the binary that are not precompiled in.

GitHub Issuen/a
TypeBug
PriorityMedium
StatusClosed
ResolutionDuplicate
Resolution Date2013-08-02T21:00:11.000+0000
Affected Version/sRelease 2.0.1
Fix Version/sn/a
ComponentsTooling
Labelscore
ReporterRussell McMahon
AssigneeIngo Muschenetz
Created2012-05-07T12:12:17.000+0000
Updated2017-03-22T22:15:12.000+0000

Description

Comments

  1. Stephen Tramer 2012-05-21

    This ticket requires some actual information about the requested feature. The summary is not enough.
  2. Russell McMahon 2012-05-21

    Not critical anymore as we have been moving to commonjs so being compiled into binary not an issue. However the bug still is valid but on a low priority. Currently we are scanning the resource folder and when we see a JavaScript file *.js it is bundled in the binary and not available through the FileSystem poof - it automagically disappears so the following will not work: ... // bring in selector engine file = Ti.Filesystem.getFile(Ti.Filesystem.resourcesDirectory, "lib", "sizzle.js"); eval(file.read().text); ... If more info is needed Blain explained the problem to me so understands what is sup here.
  3. Sindre Sorhus 2012-07-05

    I got hit bug this bug. I have a .js file I use to inject some JS into a webView, and it worked perfectly on the Simulator, but on the device nothing happened. Finally after trying everything, I found this ticket. Can this please get fixed, or at least documented, so no one else have to waste time on this. For those wondering, the workaround is to just rename the .js file to another extension, like .txt.
  4. Chris Barber 2013-08-02

    Dupe of TIMOB-2478.
  5. Lee Morris 2017-03-22

    Closing ticket as duplicate and links to the related ticket have been provided above.

JSON Source