jsx not able to watch subdirs about react

[benjamn]

Are there any .js files in src/ yet?

Also potentially useful: what node --version are you running, and what OS?

[hojberg]

There is a file in src which builds when not using a subdir in the public dir.

node version is 0.8.23 and im on OS X Mountain Lion

[benjamn]

Installed 0.8.23 but no luck reproducing. Will try on a Mountain Lion machine tomorrow. Thanks for the report.

Do you see this failure with an empty .js file? If using an empty file makes the failure go away, perhaps you can try cutting out different parts of the file to figure out the minimal contents that trigger the failure?

It could be a problem with fs.watch on Mountain Lion, though. That's my hunch.

[benjamn]

One more idea: the module cache might have gotten into a bad state somehow. Try clearing it by deleting the directory ~/.commoner/module-cache?

[hojberg]

The same file builds fine if I use jsx -w src/ public (note the lack of public/js).

Deleting that directory didn't work for me.

[benjamn]

I know this is still broken. Still working on a fix.

[hojberg]

❤️

[hieu]

I had same problem on ubuntu. Yesterday "jsx --watch" worked just fine for me. Today when I ssh-ed again and ran "jsx --watch reactjs/ js/" it just silently does nothing.

[jeffreylin]

@hojberg @hieu - I was having issues w/ vim file writes not being caught so I hacked together https://github.com/jeffreylin/jsx_transformer_fun - Feel free to try it and let me know if it works (Haven't had the time to test on Ubuntu yet...) - We might use the file watcher in that repo in Commoner / JSX in the future.

[hieu]

@jeffreylin 👍 Work like a charm. Thank you very much!

[hojberg]

Ok. I think I now know what the issue is.

jsx created a .lock.pid file in the output directory. If that file is still there when running jsx again it will quick silently.

[hieu]

Awesome!