Rudy Ges

That's unfortunate :confused: Maybe now that null safety is in the compiler we could revive this but only when null safety is `Strict`? cc @ncannasse

I don't mind keeping lix and non-lix in sync myself (and adding a CI check) but I do want a non-lix workflow to be available too

Updated the PR: * Updated base branch and libs versions * No longer removing lix/vshaxe-build, just providing alternative * Outdated libs should make CI fail pretty much all the time...

Oh look, a project still setup to use travis :grin:

With what version of `haxelib`?

#12031 has been closed again since your message, so it should be an option

With what version of Haxe compiler?

You might want to try nightlies instead. Haxe compilation server has some issues on 4.x, most were fixed on nightlies

Ok, now that's interesting. Is that with CodenameEngine?

Would need a proper repro; downloading gigabytes to _maybe_ repro the issue (not even sure how exactly) isn't really practical.