switchx support project-local copies of Haxe, or is it designed just to switch a global context of Haxe between versions?
This is important, because Project A might use Haxe 3.4.4, while Project B is on bleeding edge, and they may be building at the same time on the same system.
npm-haxe has worked well for me, except the Haxelib it includes is not compatible with Haxe 3.4, and I find that the versioning is a bit off-putting. I would like to be able to
npm install firstname.lastname@example.org and know that’s the version used, but I understand why this is so.
TypeScript has a good workflow, where you
npm install --save-dev typescript and forget it. I think
npm install --save-dev haxe has potential to be that easy… if it gets updated with a newer Haxelib and a newer default Haxe version.
"haxeDependencies", but I agree with Philippe that distributing through NPM would make sense. That’s one reason I suggested the idea of
@haxe/<lib> like TypeScript’s
@type/ namespace, but we would need to get it sorted out right before starting, since NPM won’t allow a re-release of the same version number.