5 ms·

Draft.js: map changes in the filesystem to events on the client

• jessaustin 14y ago
  I find it a lot cleaner than Cmd + Tab, Cmd + R Is that all this is? That seems like a fair amount of work for a trivial result.
  • state 14y ago
    Ha! Hopefully it's a lot more than that in the long run. But that's the first thing it replaced for me.
  • myhf 14y ago
    Pressing Cmd+S, Cmd+Tab, Cmd+R is a fair amount of work too. It only takes a second, but one second can be enough to discourage you from checking the results of a change. If that change doesn't do what you thought it would, you could have to track it down after leaving the context, losing entire minutes. I've been using this auto-reload tool, and it makes for a very smooth workflow: https://github.com/brunch/auto-reload-brunch https://github.com/brunch/auto-reload-brunch
• richo 14y ago
  > Atomic You keep using that word, I don't think it means what you think it means.
• NinetyNine 14y ago
  Is something like this possible locally with the new FileSystem APIs?