1. No need for line 22-43 (helpers/components.js). We have `setTimeout()` and `clearTimeout()` by default. 2. Timeout should be removed on destroy or disable (line 31 helpers/subprocess.js): https://gjs.guide/extensions/review-guidelines/review-guidelines.html#remove-main-loop-sources 3. Please use `TextDecoder` instead of `byteArray` (line 3 helpers/data.js): https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder 4. Please don't use `imports` (line 1 helpers/eventHandler.js). You can use the new way: https://gjs.guide/extensions/upgrading/gnome-shell-43.html#signals and import it with: ```js import * as Util from 'resource:///org/gnome/shell/misc/signals.js'; ```

Thanks for your feedback Regarding No. 2. after some considerations, i think it's not good to cancel this one, let's imagine gnome shuts down or whatever will trigger a destroy and i remove this particular timeout, then the underlying Gio Execution might block further I think those are similiar cases: https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/main/js/ui/layout.js#L762 https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/main/js/ui/status/bluetooth.js#L135

You should still remove the timeout on disable. In case you don't want the block, you can cancel it after removing the timeout.