-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Source code not recompiled on change #155
Comments
chokidar is the dependency responsible for watching for file changes, see if updating that helps. |
I updated all modules (including chokidar 2.0.4) but same issue. |
The last working commit for you is this? |
Yes.
Le sam. 18 août 2018 à 18:56, RblSb <notifications@github.com> a écrit :
… The last working commit for you is this
<668fdaa>
?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#155 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AabkGLoqDcUmjn5vjVKROoGry6Vtwikjks5uSEdRgaJpZM4WCk1H>
.
|
@carlito767 You can try install old chokidar version and set it in package.json for latest khamake, perhaps it will give some results. |
When I come back to chokidar@1.7.0, it works. But it fails with the next release (chokidar@2.0.0). |
I can not reproduce your problems but this is a good data point. I'll look into removing chokidar, it also has problems with specific chars in paths which haven't been fixed in years. |
@carlito767 You might want to check 15 chockidar commits to identify the problem (this is 4 tests if you start from the middle of the groups) |
Also, try this khamake branch https://github.com/RblSb/khamake/tree/chokidar_fix |
I found that chokidar 2.0 supports only posix slashes, so this actually should help. |
I tried your fix and it works! Thanks! |
Hi,
I recently updated my project to the latest Kha and the source code is not recompiled on change anymore. Here is the batch file used to build the project:
It seems related to this revision.
The text was updated successfully, but these errors were encountered: