-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with vshaxe / compilation server? #116
Comments
Would you have a sample project or just paste the task definition?
|
Well, as I wrote: splitting generally works well, I see the output:
But when I compile a second time without changing anything and using default build task from vshaxe, I only get:
So no more splitting. If I change something in the code splitting works again. I think by default vshaxe uses the compilation server for building that is also used for code completion and caching. If I switch that off with You're right about Thanks for making this tool available. Are you still using it yourself as well? |
So second time does the JS output look complete? e.g. just not split? Unfortunately I don't use it much myself anymore... Job doesn't include any Haxe now. |
Yes, exactly. With |
I tried modular for a very simple code splitting setup. Pure haxe and I just want one class splitted into a separate file. Worked nicely with
Bundle.load
.But when I compile again from vshaxe (default task) the code is not splitted anymore. I get one complete file then. When I try
haxe build.hxml
from the command line it works. So I thought it might have to do with the compilation server or cache. Adding"haxe.enableCompilationServer": false
to a settings.json makes code splitting work every time. Is this a known issue?Also
-D js-es=6
seems to mandatory for loading files. Is this correct?The text was updated successfully, but these errors were encountered: