Jan Keromnes

@nt1m mentioned we now have https://github.com/mozilla/gecko as well, which solves git-cinnabar's GitHub-incompatibility issue.

Thanks @Gama11! Following these official instructions, we initially got this: ``` $ git clone --recurse-submodules https://github.com/vshaxe/hxcpp-debugger $ cd hxcpp-debugger $ git checkout 1.2.4 $ npm install $ npx ovsx publish...

Thanks @Gama11! So, in trying to re-package `vshaxe.hxcpp-debugger` ourselves (option 3. from https://github.com/vshaxe/hxcpp-debugger/issues/26#issue-753304314) we're now at this stage: ``` $ git clone --recurse-submodules https://github.com/vshaxe/hxcpp-debugger $ cd hxcpp-debugger $ git checkout...

> You don't need to run `lix download` manually since it's a postinstall step already. Aha, thanks. I tried that in order to fix the `/bin/bash: haxe: command not found`...

> I don't see how that could help. My current theory is that for some reason, `lix download` is not being run after `npm install`, or it has an error...

Ok, here is the error that prevents `lix download` from working properly: ``` $ npx lix download Error: Command failed: npx lix download Version stable configured in /home/runner/haxe/.haxerc does not...

What should be the correct working directory? The ‘npx lix download’ above is being run [in the root of this repository](https://github.com/open-vsx/publish-extensions/blob/35f92c7be6cfc725e887f36acfe8763bc4251d56/publish-extensions.js#L123).

> Can you reproduce this locally, or does that only happen on your CI environment? I tried reproducing this locally in a minimal Dockerfile: ```Dockerfile FROM ubuntu:focal SHELL ["/bin/bash", "-c"]...

Aha, thanks @Gama11. Would you have any ideas: - how to get `haxe` in the `1.2.4` tag (without using `lix`)? - when the next release (with `lix`) will be published?

> Well, it's not just about getting Haxe, also other dependencies (three in this case). I doubt you want to maintain that. Well, we're already maintaining custom prepublish commands for...