change to this file were not saved to file system error in google chrome version 30.0.1599.101 m

Question

Image Notification

In the google chrome version 30.0.1599.101 m i am not able to save the changed js file. On saving the js file i got yellow triangle symbol with \"chan

Answer 1

Tonight, I accidentally managed to fix this problem, just open the file on the disk and save it with a simple change even with a space. Refresh the page in Chrome, Chrome will link it(The file) to the disk.

Answer 2

Using Ctrl + F5 to clear the browser cache worked for me.

Answer 3

Something to note: if you are making dynamically loaded JS available in devtools via the helpful: //# sourceURL=Example.js comment, this network to local mapping will not work.

Note: Notice the "//# sourceURL=dynamicScript.js" line at the end of dynamicScript.js file. This technique gives a name to a script created with eval, and will be discussed in more detail in the Source Maps section. Breakpoints can be set in dynamic JavaScript only if it has a user supplied name.

https://developer.chrome.com/devtools/docs/javascript-debugging

When you're using sourceURL, you can't actually find the respective JS file in the Sources tree where you might expect it to exist. It is available to open via the "no-domain" tree, however (or quick open with CTRL/CMD+P).

I'm still looking for a solution.

Answer 4

Happened to me too. After picking the workspace directory, I also mapped the file from the "Source" panel of Devtools to its filesystem equivalent (using right-click on the file, from the file tree). It solved my problem.

Answer 5

In chrome > 63, accepted answer option is disabled. In later should be done through workspaces.

Answer 6

The easiest solution I found to this problem:

(keep in mind, I was manipulating an html page that lives on my machine)

• open the associated html page from the command line so the page displays
  • for mac, that's simply $ open <name>.html
• open Dev Tools
• open Sources tab
• in Page, open a new .js file there with whatever name you need
• write in some text and save

This worked for me. Yes, I had to create a new .js file, but my directory locally recognized it was there when I pulled it, and my editor was updating in real time with the dev tools each time I saved either. At that point, my editor and the dev tools source tab had become one thing.