What’s your elevator pitch for this product? In the article you mention really fast client-side changes since you’re skipping the entire build toolchain, and the publish button looks really helpful for internal teams sharing around prototypes. But I’m curious, how would you try to persuade someone to use this over just using VSCode or Atom? I expected your blog post to go over that but it doesn’t really.
Windows support isn’t too far off (it used to work with Windows). The only thing I’d need to figure out is (1) ngrok on windows and (2) searching through the source tree with grep (or the Windows equivalent)
Also hoping for Windows support, since I couldn’t properly test this package because of that issue.
Haven’t had time to look after the code and send a PR but it would be nice if you could take a look on this matter
I don’t think it’d be possible for 1.5 to be even close, unless it implements a single file fast recompilation path (which is basically what reval does). Also, Reval doesn’t refresh the page, which for some apps can save a lot of time. I go pretty in-depth on how things work in the blog post.
A virtual DOM for Blaze won’t really do much for reload speeds, since it’s not related to code recompilation. Would be nice to have though
Haven’t had the time to try, but findstr seems the most similar command that is available in windows natively. Another solution would be to use an npm package with no binary dependencies (something like this or this maybe?)
Just tried it out on komentify and it worked out-of-the-box! Great stuff.
One thing I’m unsure about, which is: When I’m editing code the cursor automatically jumps out of the editor after saving and reloading the template. This makes editing templates kind of hard, anyone else experienced that?