I have literally never gotten this error, but after installing an update for my computer, this error pops up when attempting to play-test my game. Any ideas?

It appears that because the pathname has commas, that it is not correctly being linked to in my project.

I have set it up in the .vscode/settings json:

{
	...
	"lime.executable": "C:/HaxeToolkit/haxe/lib/lime/7,5,0/templates/bin/lime"
}

and I get this error:

Notice that the path gets cut off at the comma?

Temporary solution:

I just put the lime executable in my environment, but that's not what I wanted to do.

I suppose I could move the executable out of that folder? Not sure.

I am trying to use kade engine but everytime i try to build something using Visual Studio code, it keeps putting me at this message

so then i put in --dce std, and then this happens

What do i do?

When I want to test a sample project (html5) with vscode(I don't have any issue with flashDevelop) I see this error
This site can’t be reached
localhost refused to connect.
this my lunch.json codes

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "pwa-chrome",
            "request": "launch",
            "name": "Launch Chrome against localhost",
            "url": "http://localhost:8080",
            "webRoot": "${workspaceFolder}"
        }
    ]
}

It dispays this list of dependencies:

While the real list of dependencies is that:

In project I ise this dependencies:

I faced with this issue on different devices and on different Haxe language versions. I tried to reinstall Haxe and all dependencies, reinstall all VSCode extensions, connected with Haxe, but everything keeps don't work. Also it ruins Haxe language server, because it tries to find libraries, that not installed and not used at the moment.

Was trying to debug hashlink target and got nothing on stable version of the extension. After some hours I was able to fix the problem by using dev version of the extension.

Wat did not work for me:

Lime 8.0.0; HashLink 1.12.0; Hashlink debugger 1.3.4; Lime extension 1.4.3

What works:

Lime 8.0.0; HashLink 1.12.0; Hashlink debugger 1.3.4; Lime extension a117ef0

rather than having my src and Project xml at the top of my workspace, it's nested 1 folder deep in the test folder. also in the workspace is a lib folder which I marked as a dependency in my openfl project with <classpath path="../lib/src" />

this works fine in open fl, the project builds and I can even debug and breakpoint in both directories through vsCode, but when I import com.geokureli.LibClassTest; I lose code completion

as soon as I delete the import, code completion works again

When I try to debug a simple OpenFL application with the HTML5 target and Firefox as the debug browser, I get the notification:

Debugging HTML5 with Firefox requires the "Debugger for Firefox" extension

However, I already have that extension installed. Clicking on the "Install Now" action button in the notification only makes the notification disappear: no other effect occurs. I tried uninstalling the firefox debug extension, triggering the notification, and clicking the install button, but the result was exactly the same (nothing new was installed).

This behavior clued me in to the potential that the extension was being mis-identified. Due to the following line, I believe that this diagnosis is accurate:

Notice how, when navigating to this url: https://marketplace.visualstudio.com/items?itemName=hbenl.vscode-firefox-debug

You are redirected to: https://marketplace.visualstudio.com/items?itemName=firefox-devtools.vscode-firefox-debug

Looks like the publisher name has been changed from hbenl to firefox-devtools.

status bar items for the current build target, configuration (release, debug or final) as well as an option for additional flags or defines, are not present

Every time I try to build it says "No build task found. Press "Configure Build Task" to define one.

Attempting to build with the lime extension on Windows results in:

Creating D:/Projects/SiON/Export/windows/obj/obj/msvc-debug-ncxp/__pch/haxe/hxcpp.pch...
'cl.exe' is not recognized as an internal or external command,
operable program or batch file.
Error: Could not create PCH

However if I open a command prompt and simply type lime build windows within the project root, it launches the compiler just fine.

This issue seems to be isolated to windows (or a particular magic environment of windows), as on mac I can build the macOS target from with VS Code.

Any ideas?

Installing this extension makes vscodevim.vim stop working.

I have no experience with VSCode extensions, not sure I can help much.

Is there any way I can help on fixing this?

Since the MS Edge update on Jan 15 something broke.

Hi,
I just downloaded the latest haxe and lime, got VSCode with the lime, hashlink debugger and haxe extensions, created the lime simpleImage test project and tried running it in VSCode (F5) - and it does nothing with no output.

After spending some time on this problem I looked at the source for the lime vscode extension and it looks like it's not looking in the correct place for hl.exe - Lime 8.0.0 has it in "templates\bin\hl\Windows64" but the extension is looking in "templates\bin\hl\windows".

Like I said, there's no output to tell you this. I fixed it for now by just renaming the folder from windows64 to windows.

Hope this helps.

Thanks,
Greg

I get an error in the Lime extension output that reads:

Error: Command failed: lime display E:\path\to\Project.xml windows -debug -nocolor -Ddisable-version-check --haxelib=hxcpp-debug-server
Error: Incorrect number of arguments for command 'display'

It appears the call of the lime display command is being formatted incorrectly.

Right now I can add lime project dir to current workspace with Lime: Open Folder. Though I get the error Failed to create new project. Workspace folder "my-project" is not empty. the dir is added and vscode allows to use Lime command on it.

But when I manually add a project dir to the workspace (with vscode File -> Add folder to workspace), Lime is not active and Lime: Open Folder command doesn't work (I get the same error Workspace folder is not empty).

lime ext v1.5.0
vscode v1.79.2

If the user hasn't run haxelib run lime setup, the extension does not work because the extension currently requires the lime alias to exist. However, to help people get started more easily, I think that the extension should fall back to using haxelib run lime when Lime is installed, but the alias is missing.

I understand the how running lime instead of haxelib run lime looks nicer, from an aesthetic perspective. However, it's an extra step that doesn't seem strictly necessary. Ideally, if the alias is there, it should be used. Otherwise, the longer command can be a fallback.

The fewer steps for a developer to go from having nothing Haxe-related installed on their system to getting an OpenFL "hello world" running, the better. The more steps there are in that process, the more likely someone will just give up in the middle.

Some folks in the Feathers UI community have reported that they are doing exactly that: They're giving up for now and hoping that more experienced developers will write better tutorials. Removing this step from the process seems like it should help. Not only will fewer users quit in the middle, but it will make tutorials shorter.

Relatedly, I added Lime as a dependency of Feathers UI in haxelib.json because both HaxeDevelop and VSCode need it for code intelligence to work properly, and that makes for one less thing for users to install manually.

By the way, I removed the lime alias from my system, and HaxeDevelop still works fine, so they must be using haxelib run lime.

I've only been able to reproduce this on Windows, but I can reproduce it reliably with the following steps.

1. Run lime create SimpleImage to create a simple project.
2. Open the project in VSCode. Go to the Run and Debug tab, create a simple Lime launch option, and test that the program builds and launches.
3. Navigate to project.xml and add the following line. Here we're using an example string, but in a real application, this could be tied to a condition or be inside a <section> block.

<echo value="Hello, world!" />

4. Attempt to build and run the project again.

The project will build, but VSCode will not launch the program, as it will indicate a build failure:

This is logical for the <error> tag but not for the <echo> tag, which is used to provide informational messages to the user and does not indicate a build failure.

Hi, I'm experiencing an issue with the language server. It usually happens for any lime/flixel project I open in VSCode, on Linux. Occasionally it starts working fine but then randomly stops working again, but I have no idea what causes it to randomly start working.

It is slightly similar to #35 but that seems to be caused by a different issue.

Firstly, I should mention that I don't experience these issues with the regular haxe extension.

Here are the exact details:

1. I open up a lime/flixel project which compiles perfectly fine via the cli tools. For example, the template lime project. (lime create project)
2. I get an error pop up saying:

Unable to build cache - completion features may be slower than expected. Try fixing the error(s) and restarting the language server.

3. If I try to build the project, it gets stuck at Executing task: lime test linux --connect 6000 and nothing happens. Completion dosen't work either.
4. If I click retry, or if I manually restart the lanugage server, the pop up appears again.
5. If I click Show Error, it shows me the haxe output:

Haxe language server started
Haxe Path: haxe
Using --server-connect
Haxe connected!
Listening on port 6000
Failed - try fixing the error(s) and restarting the language server:

Failure("Couldn't connect on 127.0.0.1:6000")
Client connected

and in verbose mode:

Haxe language server started
Haxe Path: haxe
Using --server-connect
Haxe connected!
Processing Arguments [--display,{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"supportsResolve":true,"exclude":["zpp_nape"],"maxCompletionItems":1000}}]
 0,  x: Cached 0 modules
Completion Response =
{"jsonrpc":"2.0","id":0,"result":{"result":{"methods":["display/definition","server/contexts","server/moduleCreated","server/invalidate","server/module","server/files","initialize","display/completion","typer/compiledTypes","display/references","server/modules","server/memory/context","display/completionItem/resolve","display/typeDefinition","server/memory","display/implementation","display/hover","display/package","display/signatureHelp","server/type","server/memory/module","server/readClassPaths","server/configure"],"haxeVersion":{"major":4,"minor":3,"patch":0,"pre":"rc.1","build":null},"protocolVersion":{"major":0,"minor":5,"patch":0}},"timestamp":1664644875.022806}}
Stats = 0 files, 0 classes, 0 methods, 0 macros
Time spent : 0.000s
Processing Arguments [--display,{"jsonrpc":"2.0","id":1,"method":"server/configure","params":{"noModuleChecks":true,"print":{"completion":false,"reusing":false},"legacyCompletion":false}}]
 0,  x: Cached 0 modules
Stats = 0 files, 0 classes, 0 methods, 0 macros
Time spent : 0.000s
Listening on port 6000
Processing Arguments [--no-output,--each,--no-output,-main,ApplicationMain,--macro,lime._internal.macros.DefineMacro.run(),-cp,/path/to/project/.haxelib/lime/8,0,0/src,-D,lime=8.0.0,-cp,Source,-D,tools=8.0.0,-D,lime-canvas,-D,howlerjs,-D,no-compilation,-D,disable_preloader_assets=1,-D,lime-webgl,-D,lime-dom,-D,lime-howlerjs,-D,lime-html5,-D,html5,-D,web,--connect,6000,-js,Export/html5/bin/Test.js,-cp,Export/html5/haxe,-D,html5,-D,html,--cwd,/path/to/project]
Uncaught Error : Failure("Couldn't connect on 127.0.0.1:6000")
Failed - try fixing the error(s) and restarting the language server:

Failure("Couldn't connect on 127.0.0.1:6000")
Processing Arguments [--cwd,/path/to/project,-D,display-details,--no-output,-main,ApplicationMain,--macro,lime._internal.macros.DefineMacro.run(),-cp,/path/to/project/.haxelib/lime/8,0,0/src,-D,lime=8.0.0,-cp,Source,-D,tools=8.0.0,-D,lime-canvas,-D,howlerjs,-D,no-compilation,-D,disable_preloader_assets=1,-D,lime-webgl,-D,lime-dom,-D,lime-howlerjs,-D,lime-html5,-D,html5,-D,web,--connect,6000,-js,Export/html5/bin/Test.js,-cp,Export/html5/haxe,-D,html5,-D,html,--cwd,/path/to/project,--display,/path/to/project/Source/Main.hx@0@diagnostics]
Client connected

A new Client connected message is added everytime I try to build, but nothing else. Running lime test linux --connect 6000 or even haxe --connect 6000 in the terminal also hangs. But there is never a Client disconnected message.

Also, it's not like there's nothing on the port, the port is in use by vscode: TCP 127.0.0.1:6000 (LISTEN)

Also, there are no errors in the vscode developer console.

I have seen nothing about this anywhere. For whatever reason, it appears to be showing the name of a parameter before showing the parameter value. Sometimes it is able to be double-clicked to insert itself into the code, other times it's just there in an non-interactable state. This is specifically is tied to the Lime extension as disabling the extension causes this to no longer happen. This is incredibly annoying, how can I get rid of this?

Would be great if you could add the electron target.
I know it's possible to add in openfl.lime-vscode-extension-1.2.1\bin\lime-vscode.js, but would be great if you could add by default.

Hi! For a few months Hashlink debugging on MacOS has been integrated. Someone pointed me to a issue with Lime and I found that there still is a legacy OS guard in the code. You can safely remove this block:

https://github.com/haxelime/lime-vscode-extension/blob/c6c3581ae6f556fe56a1bd97827d973e8523d62a/src/lime/extension/Main.hx#L874

Thanks!

This is a case where the new error is perhaps a bit misleading:

Too bad Lime handles -lib on its own, otherwise it could just be passed onto the Haxe Language Server, which would then create a proper diagnostic from it in the problems view. But I guess there isn't really a way for lime display not to fail here because of its custom lib handling...

using Lime 8.0.0
lime setup hl asks where HashLink binary path is.
When you try to debug HashLink in VSCode, it is still looking for it in C:/HaxeToolkit/haxe/lib/lime/8,0,0/templates/bin/hl/windows/hl.exe

Right now, the extension just fails silently if that's not the case. It should show a helpful error to the user so he knows what's going on.

The extension fails to initialize on Windows if you are using lix-pm to manage the Haxe and libraries versions. I changed the lime.executable setting to lix run lime but it continues to spam the following message: Setting up Lime alias…

I've managed to "fix it" by commenting out the following block

Not sure if this is a bug as such, but could't find your contact info - apologies if there is a better place to ask this -_-

1: This extension is great. Thank you.

2: "lime test" is the recommended way to build apps right now right, but I found that by manually running a compilation server with haxe --wait -v 6000 and then adding <haxeflag name="--connect" value="6000"/> to my project.xml file things got sped up a lot. Now, because your plugin is presumably running an auto-complete server already, is there some way to get it to build using this without manually having to run my own server?

I am working on a project called PickHaxe, for developing Minecraft mods using Haxe.

I opted to include workspace parameters in a project.xml file, which works great, but causes issues as the Lime extension complains that the project configuration is invalid.

I use a different top-level XML tag for my projects, so ideally that could be used for detection.

Should be possible to provide this via https://marketplace.visualstudio.com/itemdetails?itemName=redhat.vscode-xml + an XML schema for the project.xml format.

After an auto update to 1.2.0, I no linger had a build command. Instead of what I usually got:

I got this:

After turning the extensions autoupdate off, I was to able to find in my Time Machine backups versions 1.0.8 and 1.1.0. Manually reinstalling either one restored the build command was restored and worked for both of those.

In the VSC Marketplace, you should be able to install older versions and/or place visix versions of all versions on GitHub for easier reinstallation of earlier versions.

I cloned Lime from git and set the folder where I checked it out as library path for dev version in haxelib:

haxelib dev lime /path/to/lime

I created another project that had Lime as dependency and vshaxe dependency explorer shows lime (dev), as it should. After a while, maybe few days, I installed latest Lime version via haxelib and removed dev:

haxelib dev lime
haxelib update lime

Now Lime is at 7.3.0 but when I open my project I still see lime (dev) there and it still points to the folder where I cloned Lime (I didn't remove the folder). This hasn't changed after I restarted VSCode, my workstation, my parrot or my cat. I even left out for an hour to play ball and when I got back it was still there 😉

I notice when loading the project that very shortly dependency explorer shows Lime version 7.3.0 and then reverts to show lime (dev).

The only way I found to fix this is to switch from Lime "Haxe Completion Provider" (which I use by default when working with Lime projects) to Haxe completion provider and then switch back to Lime completion provider. Restarting VSCode does not work.

In any case, if this is not lime-vscode-extension bug, the trick with switching completion providers might help if someone else has the same issue.

This happened when loading VS Code when loading a project containing Haxe code

If the Neko target is selected, Run without Debugging shows the notification "Debugging Neko is not supported". However, I'm not asking it to debug. I just want to launch it, like if I ran lime test neko from the command line.

When choosing Run without Debugging, the debug configuration will have noDebug set to true. That can be used to determine if debugging is necessary or not.

This would require special display argument handling (display argument providers with a document selector?).

Apologies if this is not specific to this extension. I'm working on a HaxeFlixel project and trying to figure out where responsibilities end for each piece of this setup.

I am trying to get a dev environment set up. I can currently launch my project through the build task in tasks.json:

{
    "type": "lime",
    "command": "test",
    "group": {
        "kind": "build",
        "isDefault": true
    }
}

I'm using the Flash / Debug target. This creates my Flash .swf file and opens it immediately.

In the terminal output, I see

> Executing task: lime test flash -debug -Dfdb --connect 6000 <

If I run

ls -hartl

in the bin directory, I'll see this:

-rw-r--r--@ 1 chris  staff   707K Jul  9 17:50 Example.swf

Now, I am trying to get debugging set up. For simplicity, I am removing that .swf file before running the Build + Debug launch config:

{
    "name": "Build + Debug",
    "type": "lime",
    "request": "launch"
}

This config prints the following in the terminal tab, but does not launch the .swf.

> Executing task: lime build flash -debug -Dfdb --connect 6000 <

And in the debug console I see

running /Users/chris/Documents/Development/Example/export/flash/bin/Example.swf
Error: Command failed: "/Users/chris/Documents/Development/Example/export/flash/bin/Example.swf"
/bin/sh: /Users/chris/Documents/Development/Example/export/flash/bin/Example.swf: Permission denied

And if I look at Example.swf's permissions I now see:

-rw-r--r--  1 chris  staff   707K Jul  9 17:53 Example.swf

Essentially, missing the '@' sign and seemingly, the permission to execute. Any idea how to make the launch configuration create the .swf with the proper permissions, assuming that is the problem?

Right now, code completion relies on lime update having happened. The Lime extension should do this automatically when necessary, since people keep running into this error that causes the completion cache to fail building:

Building Cache...
Type not found : ApplicationMain
Failed - try fixing the error(s) and restarting the language server:

Type not found : ApplicationMain

Getting Cannot read properties of null (reading 'bitmap') after running a few times on a very simple project.

Seems to happen after a few debugging sessions and adding images to the project

Building and running via CLI with lime build html5 then lime run html5 just works.

Also is this still maintained? Seems the open issues have been here for a while without much interaction...

Currently, the project file is specified in lime.projectFile and thus only one project can be accessed by Lime build tasks at a time. Adding this as an option which is configurable on a per-task or per-configuration basis would resolve this.

Use case: I am developing with PolyMod, which has a sample folder that contains four example projects. I would like to be able to use the Run configuration dropdown to select between each of these, but each has its own project file and the current setup does not allow this.

I cloned a haxeflixel repository, I have 2 now, however when I opened it, it doesn't work.

"Lime completion setup failed. Is the lime command available? Try running "lime setup" or changing the "lime.executable" setting."

However, in the one that I didn't download, it works fine, and does recognize imports
In the one that doesnt work, errors are still detected, but imports are all subrayed by the red line.

If assets haven't changed, it should be possible to skip the update step of build / test comands entirely. The Lime extension could create a file watcher for the assets directories if it has a way to get those from Lime, and then pass some -noupdate flag on build commands if nothing has changed.

Currently lime.projectFile on Windows, at any rate, requires an absolute path when specified in a multi-root workspace *.code-workspace file. It would be great if this could be made a path relative to the location of the *.code-workspace file. That way you could version control this file:

• in a portable way
• without exposing directory structure on your system outside the repo clone

Hello. I'm currently using this extension (using the version on the extension stroe. Everything works minus one specific step in the process: no build is actually done in both tasks.

The lime test neko -debug --connect 6000 doesn't build at all. If there is an error in the code, it won't even be notified. I don't know what it is trying to connect to but what it only does is launching the last built version (or crash due to lacking .objs file -precisely ApplicationMain.n- on a clean project folder)

I have to manually do lime test neko (with or without -debug) in the console (lime is in PATH, so no issues here).

I mostly noted the issue on Windows but I'll give a try on linux again later. The project.xml file is the same as HXFlixel's, with flixel-addons haxelib option uncommented. I wonder if it's a misconfiguration from my part or just an issue within the extension.

Have a nice day.

On deletion, Lime should deactivate + unregister the completion provider.
On file changes, the display arguments should be updated (preferably not on each save / change though, especially if the user has auto-save enabled, that might flood the server with updates - maybe when the active document is changed to a hx file again).

Hi,Running the extension out the box results in this error:
Error: You must have a "project.xml" file or specify another valid project file when using the 'test' command

I am using a template, with Project.xml in the root folder. The project correctly runs in Chrome when using lime test html5 on the cmd line