arikw / chrome-extensions-reloader Goto Github PK

It looks like this just reloads the code (which is fine!) - it might be nice if there was an option to force it to reload the unpacked version and trigger the chrome.runtime.onInstalled event.

This event doesn't trigger when reloading through the plugin (for me) but does if I go to my extension and do a fresh Load Unpacked.

It would be nice to have a keyboard shortcut to reload the extension.

I am currently working on migrating a chrome extension from manifest v2 to v3 and thought extensions-reloader would be useful to me. I noticed that you're still using the old manifest format and, due to low activity on your repo, thought you might have missed the deprecation warnings. Here's the details: https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/

The biggest change is that the background page is gone and replaced with a service worker.

The background page inspector is the most important tool for extension development.
Unfortunately, when the chrome-extensions-reloader reloads an extension, it shuts everything down, including its inspector. As a result, we have to reopen the background inspector each time we save changes... which is painful and makes this extension useless

I am pretty sure there is a way to reload extensions without closing those background inspectors. For instance, the “Reload” button provided on the Chrome’s extension page keeps them opened. Any idea?

When you open http://reload.extensions in a new chrome tab and have "Reload current tab after extensions have been reloaded." enabled, it will get stuck in an endless reload loop. Please fix this.

Kind of seems like the extension is doing what it's supposed to be doing, but it doesn't seem to be working anymore. I tried to fix on my own but had no luck.

Seems kind of like two things are going on.

First, redirectUrl doesn't seem to respect chrome-extension:// URLs anymore. I was able to make a data-url work as the redirect, and I was able to make a normal HTTP URL work as the redirect, but no love from chrome extension URLs.

The second thing I tried was to just self-host the close page and redirect to it. This kind of works in that at least the redirect is respected, but the tab doesn't close in this fashion. The console offers some clue as to why: "Scripts may close only the windows that were opened by it."

Here's the HTML file I self hosted if you want to give it a try: http://static.tdg5.com.s3.amazonaws.com/close.html

I tried to look in the changelog for Chromium for reference to any of these changes, but didn't see anything, though I was mostly looking for references to onBeforeRequest.

I haven't dug into this much further and am not familiar with the extension, but if you have any other suggestions for getting the tab to auto-close, please let me know.

Thanks!

50% of the time when I use this extension (navigating to http://reload.extensions), it results in an error page saying "reload.extensions is blocked".

I downloaded the extension and confirmed that the bug does not happen at bc2c308, but it does start happening at 8d20627.

I suspect the problem is the line that returns { cancel: true } from the onBeforeRequest listener.

Screenshot

The original problem is displayed here

I found the problem lies in the reload extension.

When reloading the extension, my background javascript console is closed. This is very difficult because I have to open it again from my chrome://extensions.

When reloading the extensions from chrome://extensions, the background console does not close.

I'm a bit puzzled as to how this is supposed to work. When I click the button or http://reload.extensions, it seems to do something (buttons repopulate). However when I check my (unpacked) extension, it hasn't reloaded.

A couple of things I've tried:

• Change the name in my manifest.json and see if it updates in action popup and tooltip
• Remove a content_script and refresh the page after running http://reload.extensions

None of the above worked. Clicking Reload for my extension on chrome://extensions worked every single time. Am I missing something obvious?

When developing an extension with a content_script, I always need to reload the page after extension was reloaded.
It would be nice if extensions reloaded the current page automatically.

Or another approach: an option to reload extensions on every page reload.

It would be nice if in the options page I could select which of my unpacked extensions should be reloaded (with, say, a checkmark - or a less user-friendly options that might be easier to implement is to just enter extension IDs)

When working on an extension's settings page, reloading the extension closes the options page. It would be helpful to reopen it upon reloading, so the developer doesn't have to do that themselves. This older extensions reloader says in its description that it does this.

http://reload.extensions/ isn't working for me. I'm using Chrome v118.0.5993.88 (Official Build) (x86_64). I've tried to access that URL from the browser and a few command line tools.

Love this extension, saves so much time.

Have noticed (for a few years now actually) that the extension only reloads the content scripts which are already loaded. This is great if I change a JS/CSS file, but not when I add a new file to the manifest.json. In that case I have to go to the extensions page itself and reload manually.

Is this a limitation of Chrome's API or could this be added in a future version?

After .setEnabled(id,false) the extension itself goes blank,
maybe there is someway to spawn a process that re-enables and launches it before that?

I'm not sure if this is possible, but it would be handy if a reload icon or menu item could be added to chrome developer tools.

Would be nice if you could look at at the extension folder and detect when a file has changed.