It looks like you simply don't have the HaxeFlixel / FlashDevelop project template installed (it's not built-in). I think you can install it via AppMan.

In case somebody else runs into this and stumbles over this thread, somebody on GitHub seems to have found a fix: https://github.com/HaxeFlixel/flixel-tools/issues/72#issuecomment-565801794

You're not doing anything wrong, the Lime extension simply doesn't support HashLink debugging yet. You don't have to debug to build + run though, use the "lime test" task for that.

The PS4, XB1, and PSVita backends are now deprecated:

https://www.fortressofdoors.com/setting-boundaries-open-source-gamedev-on-consoles/

Could be the same issue as https://github.com/openfl/openfl/issues/2264 (FlxText uses an OpenFL TextField under the hood).

This can be solved by either upgrading to Haxe 4.0.0-rc.3 or downgrading to hxcpp 4.0.8. See also:

https://github.com/openfl/lime/issues/1331

Hm, you must have made that typo yourself accidentally , that issue doesn't exist in Haxelib release and on GitHub:

https://lib.haxe.org/p/flixel-demos/2.7.0/files/Arcade/Flixius/Project.xml
https://github.com/HaxeFlixel/flixel-demos/blob/dev/Arcade/Flixius/Project.xml

(it would have been noticed by Flixel's CI if one of the demos suddenly didn't build anymore)

The export folder can be rather big indeed, but it's mostly about the object files. The actual executable / bin subdirectory you would ship with releases is not very big.

There's a few fixed versions floating around, for instance https://github.com/Lythom/nape-build. Just run the following:

haxelib git nape https://github.com/Lythom/nape-build

I believe this has been fixed in Lime / OpenFL:

https://github.com/openfl/openfl/issues/2111

The fix might not have made it to Haxelib yet, so it might still require to install development builds of Lime and OpenFL.

Might be something for the OpenFL issue tracker, if you can reproduce with a pure OpenFL project / without Flixel.