Closed latentflip closed 10 years ago
yup, agreed. this is confusing. I've made some rather drastic simplifications to this library now. I think it's a lot cleaner. It doesn't try to write the built JS file to disk any more. It just caches them in memory and serves them.
This should help us avoid issues with committing built files, etc.
Also, now using browserify instead of stitch. It's more up to date and has windows support (which matters for some of our clients who host on azure).
Thanks for the feedback.
On Saturday, June 15, 2013 at 3:25 AM, Philip Roberts wrote:
Not sure if this is a setup issue in andbang, or a moonboots issue, but I didn't realise that moonboots was recompiling my package on every edit+pagerefresh (which is awesome :) ) because there's no output in the console. You just get the first:
Moonboots: app files already written. so I was killing the server on each change. Maybe you could log "rebuilt foo.js" on a page refresh when the files have been edited?— Reply to this email directly or view it on GitHub (https://github.com/HenrikJoreteg/moonboots/issues/2).
Cool! I am moving float over to browserify and loving it :)
nice :)
On Monday, June 17, 2013 at 3:19 PM, Philip Roberts wrote:
Cool! I am moving float over to browserify and loving it :)
— Reply to this email directly or view it on GitHub (https://github.com/HenrikJoreteg/moonboots/issues/2#issuecomment-19578974).
In 2.0 there is now a 'timing' mode that will emit timing events at all meaningful steps, both start and finish. Also, if the files are being rebuilt on every request, the filenames have 'nonCached' in them so there is a visual there.
In theory we could also emit a logging event during buildJS and buildCSS but I don't know that this is really needed.
Not sure if this is a setup issue in andbang, or a moonboots issue, but I didn't realise that moonboots was recompiling my package on every edit+pagerefresh (which is awesome :) ) because there's no output in the console. You just get the first:
Moonboots: app files already written
.so I was killing the server on each change.
Maybe you could log "rebuilt foo.js" on a page refresh when the files have been edited?