Alloy compiler fails

[Axemark38]

I'm trying to emulate my Android app with JSDOM but the compiler fails because of the fs-extra error Cannot copy to a subdirectory of itself (found with log level set to debug). I'm not sure how to fix it. Some help would be greatly appreciated.

ti build output

[WARN]  Unable to locate an /usr/lib/libGL.so.
[WARN]  Without the libGL library, the Android Emulator may not work properly.
[WARN]  You may be able to fix it by reinstalling your graphics drivers and make sure it installs the 32-bit version.
[INFO]  Found Titanium plugin id=ti.alloy version=1.0 
[INFO]  Deploy type: development
[INFO]  Building for target: emulator
[INFO]  Building for emulator: Small_Phone
[INFO]  Targeting Android SDK API: 34
[INFO]  Building for the following architectures: arm64-v8a, armeabi-v7a, x86, x86_64
[INFO]  Signing with keystore: /home/mark/.titanium/mobilesdk/linux/12.7.1.GA/android/dev_keystore (tidev)
[INFO]  Debugging disabled
[INFO]  Profiler disabled
[INFO]  Transpile javascript: true
[INFO]  Generate source maps: true
[INFO]  Forcing rebuild: /home/mark/Projects/test/build/android/build-manifest.json does not exist
[INFO]  Found Alloy app in /home/mark/Projects/test/app
[INFO]  Executing Alloy compile: /home/mark/.nvm/versions/node/v22.16.0/bin/node /home/mark/.nvm/versions/node/v22.16.0/bin/alloy compile /home/mark/Projects/test/app --config platform=android,version=0,simtype=none,devicefamily=none,deploytype=development,target=emulator
[INFO]   [config.json] regenerating CFG.js from config.json...
[ERROR] : Cannot copy '../tldts/bin/cli.js' to a subdirectory of itself, '../tldts/bin/cli.js'.
[ERROR] Alloy compiler failed

[m1ga]

first of all: no clue what you are doing here 😄 But since the error log is inside onLink I think you have link and it is pointing to itself? I'm also not sure if the file tldts/bin/cli.js should be in your project folder. Normally when you work with nodejs packages they should be in the lib folder because. Mabye that helps (but again, no clue what you are trying to do here, sorry 😄 )

[Axemark38]

I'm sorry if it wasn't clear enough. I installed jsdom in the lib folder with npm, attempted to start up an Android emulator with help of the VSCodium extension but fails due to the onLink function error. That file isn't the only one tripping it btw. Since jsdom needed certain Babel plugins, their files trip it too. These are not my files so I'm not exactly sure how to resolve this.

[m1ga]

I'm not sure you can run that package as it has many dependencies and as soons as one requires nodejs core modules it won't work. And like you've said it starts with this babel error for me Export namespace should be first transformed by @babel/plugin-proposal-export-namespace-from when I test it.
And jsdom is used to simulate a DOM? So you want to use it in a webview or test data that would be in a webview? A normal Ti app doesn't have a DOM as it is will native components when you create a window.

[Axemark38]

I'm only interested in jsdom's html parsing, not trying to implement a webview.

[m1ga]

ah ok, because for that you could also use Ti.XML and use it like this:

const doc = Ti.XML.parseString("your html string");
const titleNode = doc.getElementsByTagName('title').item(0);
const title = titleNode ? titleNode.textContent : 'No title found';

it's not DOM parsing as you would do it in a web browser but using XML methods.

Otherwise you could even use a webview and evaljs to parse HTML inside the webview and return the parts you'll need.

But I don't think jsdom will run. Perhaps someone else finds the thread and will jump in with a solution, so lets see. Otherwise: more people use Slack for support

[Axemark38]

I'll admit.. I had no idea Titanium had that XML module. I assumed there was no way to parse directly like that. Clearly I didn't look hard enough at the documentation, sorry about that. Thanks for pointing it out, some of the methods should help me.

[m1ga]

no problem. Hope it is already enough to work with 👍