mechio / takana

Takana lets you see your SCSS and CSS style changes live, in the browser, as you type them
http://takana.io
MIT License
1.11k stars 61 forks source link

Browser and editor connect, but no refresh #76

Open lmartins opened 9 years ago

lmartins commented 9 years ago

Hi,

I am trying Takana again but having trouble getting it to work. As fas as I can tell both the browser and editor connect to the server, but no changes happen when I change my scss.

[16:59:20] [INFO] - editor server listening on 48627
[16:59:20] [INFO] - webserver listening on 48626
[16:59:21] [INFO] - installing plugin to '/Users/luismartins/Library/Application Support/Sublime Text 3/Packages/Takana'
[16:59:21] [INFO] - running on project /Users/luismartins/Sites/vagrant-local/www/webipack/htdocs/wp-content/themes/wip-homely2
[16:59:22] [INFO] - editor connected
[17:00:40] [INFO] - browser connected to project default

When I make changes to Sass I do get updates on terminal window such as:

[17:00:40] [INFO] - rendered /Users/luismartins/Sites/vagrant-local/www/webipack/htdocs/wp-content/themes/wip-homely2/build/css/main.css

Am I missing something?

JamesJosephFinn commented 9 years ago

Same for me, except my project path is ~/Documents/project

I get the same terminal output as you. Everything looks good, but no changes to .scss files are reflected in the browser.

All of my .scss files reside in project/scss.

I open index.html using the file:// protocol, although the demo video shows using localhost.

When I make changes to styles.css (which resides in project root /project ), I can make live changes all day. But no go for .scss. What gives?

JamesJosephFinn commented 9 years ago

@lmartins Are you seeing the following error in your console:

[Error] Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:48626/live/main.css.map

I am. The takana.js script is making the request. I'm filing a bug report.

ob7 commented 9 years ago

try chmod your scratch directory, it sounds to me like the css files arn't being written after changes, therefor no browser update.

Also make sure the path to your project does not contain spaces, as I have found this causes problems with writing the files.