search

NV / chrome-devtools-autosave

Auto-saving CSS and JavaScript changes from the Chrome Developer Tools
MIT License
1.04k stars 89 forks source link

Log message appears but JS/CSS file isn’t updated on disk #54

Closed simonexmachina closed 12 years ago

simonexmachina commented 12 years ago

I get the following log message appearing in the server, but the file isn't updated on disk with the updated CSS:

27-05-2012 15:47:27: Saved a stylesheet to /Users/simonwade/dev/Projects/APlus/Repository/aplus/public/campaigns/first-month-free/css/style.css

Also, the log messages only appear for me when I press Cmd-S to initiate the Save.

NV commented 12 years ago

That’s weird. Is it the same for all files?

simonexmachina commented 12 years ago

Yes, for both CSS and Javascript. Happens in both Chrome and Chrome Canary. Also doesn't work when your extension is not installed as well. You can see the source files I'm editing here. Really hoping to get this to work, so any advice you can offer is appreciated.

NV commented 12 years ago

Also doesn't work when your extension is not installed as well.

It shouldn't. When the extension is not installed you’re not supposed to see any log messages in the console.

I just reinstalled chrome-devtools-autosave/latest.crx and the server on Chrome 21.0.1145.0 dev. I downloaded your archive and edited some CSS. It all worked well.

Troubleshooting. If you have some errors it might give me some clue.

franciscolourenco commented 12 years ago

It doesn't happen on normal channel of chrome for me..

NV commented 12 years ago

Could you try the latest version from the repository and tell how it goes?

franciscolourenco commented 12 years ago

I tried to run the latest version of the server but I get http://127.0.0.1:9104 is already in use. Exiting.. Tried to kill 488 0.0 0.3 3040156 11304 ?? S 6:51PM 0:00.10 node /usr/local/bin/autosave with kill, sudo kill, kill -9 but the process just restarts with a new PID. Even tried to restart the system, but the process just starts at login..

NV commented 12 years ago

The latest version of the server starts immediately after installation and loads at login. You don’t need to run it manually any more. I should make instructions clear.

If http://127.0.0.1:9104 shows something than everything is all right.

However, on Mac OS X you can kill the server by 

launchctl unload ~/Library/LaunchAgents/com.chrome.devtools.autosave.launchd.plist
franciscolourenco commented 12 years ago

Shouldn't login autostart be optional?

franciscolourenco commented 12 years ago

The latest version from the repo, behaves the same way on the latest canary (21.0.1154.0); it overwrites the file, but without changing the values.

On stable chrome it works fine with file:// but can't make it work with localhost. Is somethign wrong with ^http://localhost/?

simonexmachina commented 12 years ago

So I've updated to the development version and I get the same behaviour. It prints "Saved a stylesheet to /Users/simonwade/dev/Projects/APlus/Repository/aplus/public/campaigns/onemonthfree/css/style.css", the file is modified, but the changes are not written to the file.

NV commented 12 years ago

Now I can reproduce this bug on Chrome 21.0.1155.2 dev. https://code.google.com/p/chromium/issues/detail?id=130263 Works well in Chrome stable, though.

pixeldrew commented 12 years ago

Same issue here in Chrome Canary. It seems that the POST request sent to the server seems to not have the updated rule. Google version 21.0.1156.0 canary. Has the API changed?