xpl / crx-hotreload Goto Github PK

See this PR by @dmitry-pogorelov: #4

Some users (@acfasj) report that the parameter change does not work as expected... Unfortunately I currently do not have time to test & verify this thoroughly, so I would appreciate any feedback.

Просто нет слов)! Спасибо)! ГОДЫ МУЧЕНИЙ....

Support specifying or limiting which files to watch, so it doesn't reload before a build is complete.

I get a pop up error message box from chrome on reloading my extension.

This is my manifest.json, https://gist.github.com/xush6528/b2721f54f34fc740e4e2facdd44cb800

I wonder what other requirements this solution has.

Checking for timestamps doesn't seem to work anymore — the file entries in PackageDirectoryEntry no longer seem to contain the lastModifiedDate property.

Chrome 63

If I was developing a new tab plug-in, runtime.reload would reset my new tab to the default

Your hot reload solution is great, and it worked for me wonderfully when I was building out the Google Extension tutorial.

However, now that I am building a more complex extension with webpack, I am not able to get hot reloading to work. After some research, I found that the hot-reload module stops polling after I run npm run build. That command removes, and rebuilds the dist folder that houses all my unpacked extension files.

The hot-reload file is added as one of the entries in webpack.config. So, when the app is rebuilt, I wonder if hot-reload.js gets deleted?.. Or, it loses the connection to file system because now it's a different dist folder?

Wondering if you, or someone has run into this problem before, or if you have ideas on how to solve it.

Make it importable from the NPM module, as it's suggested here.

Tested this and it worked! 🎉

import "crx-hotreload";

I think the Readme can be updated!

Heya! Thanks for making this =D. It doesn't look like the latest changes (from this commit) have been published to npm. Do you have plans to do that anytime soon?

Apparently, this awesome extension won't work with Manifest v3 since it's not possible to access filesystem API from service-worker