-
Notifications
You must be signed in to change notification settings - Fork 47.4k
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
jsx --watch crash #957
Comments
AFAIK this is a "bug" with |
Does it work again if you remove the .lock.pid file? |
@benjamn Yes it does. Oh or wait, the crashing. |
It seems like there are two ways of fixing this. We can either
I'm pretty comfortable with option 2, honestly. Thoughts, @zpao, @spicyj, @petehunt, @syranide, @mtgred? |
@benjamn Yeah, no lock seems fine for me, it could warn if it was found perhaps? Another thing to mention that has been happening to me, I'm using React through a Linux VM and accessing the filesystem through samba. When saving a file it immediately triggers a recompile before the file has finished saving, causing it to error. Shortly after it recompiles it again, so no harm, but it's worth noting. |
I'm fine with no locking. I didn't even know that existed. Do what works! |
When I run jsx --watch src/ build/ it compiles the jsx files and create a .lock.pid file in the build directory.
On the next jsx file modification, the jsx process crashes. Once the .lock.pid is present, jsx won't compile jsx files even when ran manually.
I use OSX Maverick and jsx 0.8.13.
The text was updated successfully, but these errors were encountered: