Sergey Chikuyonok

No. Source maps are good for viewing things, but not for editing. Whenever you change something in SASS or generated CSS, source map become invalid and have to be re-generated...

Re-compilation of SASS doesn’t makes sense for LiveStyle. It will be yet another LiveReload/CodeKit/etc. The goal of LiveStyle is to make a truly live (without any re-compilation) and bi-directional development....

SCSS is just an experiment I made for demo video to show the power of LiveStyle engine. It is disabled because it wasn’t tested enough and may actually break your...

1. Re-compilation is not an option: it’s very slow. With re-compilation it would be just another CodeKit/LiveReload clone. 2. Source maps must be re-compilated for each update, which it also...

Make sure you have the most recent version of LiveStyle extension for Chrome

Can you show me console log of `background.html` page from LiveStyle extension? It’s available in Chrome’s Extensions pane in Emmet LiveStyle section (with Developer mode enabled)

That’s not actually I was looking for. I need full console log from `background.html`, not the Sources

Source maps won’t help here: they good for viewing things, but not for editing. Chrome Workspaces has the same issue: every time you modify either generated CSS or preprocessor source,...

Hey guys, thanks for waiting for so long :) After a year of heavy development I’m glad to announce LiveStyle 0.9 Alpha with LESS support. Check it out: http://livestyle.emmet.io/alpha/

I think it’s a temporary Canary issue. Anyway, check out new LiveStyle Alpha: http://livestyle.emmet.io/alpha/ Current beta-extension you have no longer under development