With the new brackets shell changes to extensions are cached and therefore don't reload when you hit F5 or reload brackets. To demonstrate the issue:
alert("I am here");
Kinda a pain if you're working on an extension and just want to hit f5 to see your change.
Possibly same bug as adobe/brackets-shell#32
Reviewed - assigned to @jasonsanjose
I'll update here with a comment and update the developer docs on how to disable the cache.
Note: this issue still occurs for unit test spec files too ("*-test.js"). Same workaround applies.
Also note: the workaround only works while the Developer Tools window is open. If you close it, the bug comes back for any further changes to extension/spec code.
Ideally, we should figure out a way for brackets-shell to just automatically do whatever the "Disable cache" checkbox does (or maybe it could even be done in brackets core code, by pinging our own remote debugging URL?).
I think this is now being tracked by #1744. Closing.