In my spare time I'm working/researching about "instant feedback" in web development.
We know that JavaScript is capable to support this in a development environment, so, I love to see a project motivated to achieve that.
I'll make a bug report with the exception that raises.
Oh, another thing... amokjs.com is down. Maybe it would be a good idea removing the references to it? Because searching for information I get to an death end many times.
And it should work just fine on Linux :)
Just to grok the use case
build/server etc is optional, amok can serve just as a browser 'opener' with hotreload
v2 (http://github.com/codajs/coda) is more modular (and not usable at all currently, don't even bother installing it :P )
I imagine if I studied it long enough I could figure out how to rewrite it, but I do love reusing other people's already-working libraries :-)
Truly seperate concerns, just optionally creates its own connection if none is provided. Allowing it to act as a standalone executable, or plugin.
Yet to push but these are basically dual purpose modules.. the default export is a plugin entry point, everything else is "useful" code relating to that domain
Remember that the browser is the server
Just from a testability standpoint tho, making these work as standalone executables as-well as plugins feels great :D
Still can't make re-evaluation work without transforms/loaders tho.. arrgh javascript y u no metaprogramming ;)
@TatriX I'm on Arch as well and Chrome launches fine using Amok (e.g.
amok --browser chrome about:blank). Just a guess, but something I've seen with other projects is that they'll work with Google Chrome, but not Chromium (usually just because they're hard-coded to run google-chrome). Easy solution might be to install Chrome from the AUR (assuming that actually is the problem)
Or maybe try
amok --browser /usr/bin/chromium about:blank
And all other variants
amok simply silently do nothing
--browser chromium would do a chromium lookup (chromium-browser) in PATH
like browsersync
